shipshitdev/agent-folder-init
bundles/session/skills/agent-folder-init/SKILL.md
Add or repair .agents/ project context for an existing repo. Use for AI agent documentation, session tracking, task management, and coding standards; do not use as the primary new-product scaffold.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library agent-folder-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 6:42 AM54.7s51 files scanned
SKILL.md
- name:
- agent-folder-init
- description:
- Add or repair .agents/ project context for an existing repo. Use for AI agent documentation, session tracking, task management, and coding standards; do not use as the primary new-product scaffold.
- version:
- 1.0.0
- tags:
- agents, setup, documentation
Agent Folder Init
Create a comprehensive .agents/ folder structure for AI-first development workflows.
Contract
Inputs:
- Existing project root
- Project name and primary tech stack
- Agent platforms to support: Claude Code, Codex, Cursor, or all
Outputs:
.agents/documentation structure- Root agent entry files such as
AGENTS.md,CLAUDE.md, andCODEX.md - Summary of files created and files skipped because they already existed
Creates/Modifies:
.agents/,.claude/,.codex/,.cursor/, and root agent entry files- Does not create application source code
External Side Effects:
- None beyond local file writes
Confirmation Required:
- Before overwriting existing agent docs or config files
- Before writing outside the current workspace
Delegates To:
project-init-orchestratorwhen starting a new product repofullstack-workspace-init/npx @shipshitdev/v0when a new Shipshit.dev product should be scaffoldedagent-config-auditafter generation to detect drift or stale config
Purpose
This skill scaffolds a lean AI agent documentation system including:
- Session tracking (daily files in
.agents/SESSIONS/) - Durable project context in
.agents/memory/(one topic per file) - Agent config folders (.claude, .codex, .cursor) with commands, rules, and agents
When to Use
Use this skill when:
- Adding AI coding-assistant context to an existing project
- Setting up AI-first development workflows
- Migrating an existing project to use structured AI documentation
For new Shipshit.dev product repos, prefer project-init-orchestrator, which
routes to npx @shipshitdev/v0 and includes the standard .agents, .claude,
and .codex setup.
Usage
Run the scaffold script:
python3 scripts/scaffold.py --help
# Basic usage
python3 scripts/scaffold.py \
--root /path/to/project \
--name "My Project"
# With custom options
python3 scripts/scaffold.py \
--root /path/to/project \
--name "My Project" \
--tech "nextjs,nestjs" \
--allow-outside
Generated Structure
Documentation (.agents/)
.agents/
├── README.md # Navigation hub
├── memory/
│ └── README.md # Source of truth for durable project facts
└── SESSIONS/
├── README.md # Session format guide
└── TEMPLATE.md # Session file template
Rules and coding standards go in CLAUDE.md (repo root) and the global ~/.claude/CLAUDE.md — not inside .agents/.
Task tracking uses GitHub Issues (gh issue list, gh issue create) — not local task files.
Agent Configs
.claude/
├── commands/ # Slash commands (project-specific)
│ ├── start.md
│ ├── end.md
│ ├── new-session.md
│ ├── commit-summary.md
│ ├── code-review.md
│ ├── bug.md
│ ├── quick-fix.md
│ ├── refactor-code.md
│ ├── inbox.md
│ ├── task.md
│ ├── validate.md
│ └── clean.md
├── agents/ # Specialized agents (project-specific)
│ ├── senior-backend-engineer.md
│ └── senior-frontend-engineer.md
└── skills/ # Project-specific skills
.codex/
├── commands/
└── skills/
.cursor/
└── commands/
Note: Agent configs (agents/, commands/) are copied from the installed library bundle so projects get the latest version. Rules are not copied because they are expected to be managed at the user or repo level to avoid duplication and drift.
Root Files
AGENTS.md- Points to.agents/README.mdCLAUDE.md- Claude-specific entry pointCODEX.md- Codex-specific entry point.editorconfig- Editor configuration
Key Patterns
memory/ Files
- One topic per file:
memory/architecture.md,memory/deployment.md,memory/entities.md, etc. - Every file carries a
last_verified: YYYY-MM-DDfront-matter field. - Transient or short-lived facts add
status: temporary.
Session Files
- One file per day:
SESSIONS/YYYY-MM-DD.md - Multiple sessions same day use Session 1, Session 2, etc. in the same file.
Customization
After scaffolding, customize:
CLAUDE.md(repo root) - Add project-specific coding standards and "never do" rules.agents/memory/architecture.md- Document your architecture decisions.agents/memory/entities.md- Document your data entities.agents/memory/deployment.md- Document deployment steps and gotchas- GitHub Issues - Create issues for tasks (
gh issue create) .claude/rules/- Add project-specific rule files.claude/commands/- Add project-specific slash commands
Integration with Other Skills
This skill integrates with:
| Skill | How It Works Together |
|-------|----------------------|
| project-init-orchestrator | Routes new product requests to v0 before lower-level setup |
| fullstack-workspace-init | Uses v0 for new Shipshit.dev product workspaces |
| linter-formatter-init | Sets up quality tooling in the scaffolded project |
| husky-test-coverage | Enforces test coverage in pre-commit hooks |
Related Skills
shipshitdev/execution-validator
testing
VerifiedTrustedCommunity
Use this skill when users need to validate a launch plan, assess MVP scope, or determine if they're ready to execute. Activates for "validate my plan," "am I ready to launch," "is my scope too big," or when assessing action readiness.
24SKILL.mdUpdated Jun 4, 2026
shipshitdev/execution-accelerator
testing
VerifiedTrustedCommunity
Use this skill when users are stuck on a decision, overthinking, experiencing analysis paralysis, or need to ship faster. Activates for "should I wait," "I can't decide," "I'm overthinking," or when speed is critical and perfectionism is the enemy.
24SKILL.mdUpdated Jun 4, 2026
shipshitdev/early-hiring-advisor
development
VerifiedTrustedCommunity
Use this skill when users need to make early hires, build their founding team, determine compensation/equity, decide who to hire first, or scale from founders to first employees. Activates for "who should I hire first," "early hiring," "equity for employees," or team building questions.
24SKILL.mdUpdated Jun 4, 2026
shipshitdev/constraint-eliminator
data-ai
VerifiedTrustedCommunity
Use this skill when users need to remove customer friction, improve customer success, handle objections, design guarantees, or eliminate obstacles between customers and results. Activates for customer success issues, objection handling, or "customers can't get results" problems.
24SKILL.mdUpdated Jun 4, 2026