From wf
Detect and provide the project name from package.json or pyproject.toml. Use when you need the project name, package name, or module name for imports, paths, or documentation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wf:project-nameThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Detect the project name from configuration files and make it available as `${PROJECT_NAME}` for use in other skills and instructions.
Detect the project name from configuration files and make it available as ${PROJECT_NAME} for use in other skills and instructions.
✅ Use when:
src/{PROJECT_NAME}/${PROJECT_NAME}❌ Don't use when:
pyproject.toml (Python projects)
[project]
name = "my-package"
package.json (Node.js projects)
{
"name": "my-package"
}
Ask user (if neither file exists or name not found)
When ${PROJECT_NAME} is referenced or you need the project name:
Check for pyproject.toml at project root
[project] section with name field${PROJECT_NAME}Check for package.json at project root
"name" field at top level${PROJECT_NAME}Ask the user if neither file contains a project name
${PROJECT_NAME}For Python projects, normalize the name for imports:
my-package → my_packagefrom my_package.core import ...Other skills can reference the project name using ${PROJECT_NAME}:
# Example usage in another skill
Import the logger:
```python
from ${PROJECT_NAME}.core import logger
Project structure:
src/${PROJECT_NAME}/
├── core/
├── models/
└── services/
## Output
When this skill is invoked, provide:
Project name: ${PROJECT_NAME} Source: pyproject.toml | package.json | user input Normalized (Python imports): ${PROJECT_NAME_NORMALIZED}
## Example
**pyproject.toml**:
```toml
[project]
name = "my-awesome-tool"
Result:
Project name: my-awesome-tool
Source: pyproject.toml
Normalized (Python imports): my_awesome_tool
Usage:
from my_awesome_tool.core import loggersrc/my_awesome_tool/services/${PROJECT_NAME} throughout for imports and pathsnpx claudepluginhub mesca/claude-plugins --plugin wfDetects project type, package manager, and monorepo structure. Returns correct commands for test/build/lint/dev. Run at project initialization and cache results in state. Use before running any build/test commands.
Configures pyproject.toml for Python packages: build backends (hatchling, setuptools, maturin), PEP 621 metadata, PEP 735 dependency groups, entry points, versioning, and tool settings (ruff, pytest).
Creates distributable Python packages with pyproject.toml, proper project structure, and publishing to PyPI. Use when packaging libraries, building CLI tools, or distributing Python code.