Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From fs-dev
Agent artifact placement conventions. Use when creating plans, tasks, research, reviews, brainstorms, or any agent-generated files. Ensures artifacts go to docs/.claude/ (gitignored) instead of polluting the repo.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fs-dev:agent-artifactsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Agent-generated files (plans, tasks, research, reviews, orchestration output) MUST go to `docs/.claude/`, never the repo root. This directory is gitignored per git-repo-standards.
Agent-generated files (plans, tasks, research, reviews, orchestration output) MUST go to docs/.claude/, never the repo root. This directory is gitignored per git-repo-standards.
docs/.claude/
├── tasks/ # Todo lists, checklists, work tracking
├── plans/ # Implementation plans, design docs, architecture
├── research/ # Research results, analysis, findings
├── reviews/ # Consensus review reports, audit results
├── orchestration/ # Orchestration state, dispatch logs
└── brainstorms/ # Brainstorm sessions, ideation output
docs/.claude/<subdir>/ for generated files.claude/fs-dev-settings.json for project-specific overrides| Artifact Type | Directory | Examples |
|---|---|---|
| Plans | docs/.claude/plans/ | implementation plans, design approaches, architecture docs |
| Tasks | docs/.claude/tasks/ | todo lists, checklists, work items |
| Research | docs/.claude/research/ | technical research, competitive analysis, findings |
| Reviews | docs/.claude/reviews/ | consensus review reports, code audits |
| Orchestration | docs/.claude/orchestration/ | multi-agent dispatch state, execution logs |
| Brainstorms | docs/.claude/brainstorms/ | brainstorm transcripts, ideation notes |
Projects can customize via .claude/fs-dev-settings.json:
{
"agentArtifacts": {
"baseDir": "docs/.claude",
"allowedSubdirs": [
"tasks", "plans", "orchestration",
"research", "reviews", "brainstorms"
]
}
}
If the settings file doesn't exist, use the defaults above.
These belong at the repo root — do not redirect them:
CLAUDE.md, .claude.local.md — Claude Code configurationREADME.md, CHANGELOG.md, LICENSE — repo documentation.gitignore, .gitleaks.toml — repo configurationSECURITY.md, CONTRIBUTING.md, CODEOWNERS — repo standardsnpx claudepluginhub fyrsmithlabs/marketplace --plugin fs-devScaffolds `.agents/` project context (sessions, memory, agent configs) for existing repos. Use when adding AI coding-assistant documentation or migrating to structured AI workflows.
Generates AGENTS.md files for repository folders with build commands, testing instructions, code style, project structure, and boundaries. Only generates where AGENTS.md is missing.
Manages project directory setup and artifact organization for new or resumed projects. Creates folders like specs/, scripts/, notebooks/, manifests/, agent_memory/ and resolves project naming.