shipshitdev

agent-folder-init

4
0
# Install this skill:
npx skills add shipshitdev/library --skill "agent-folder-init"

Install specific skill from multi-skill repository

# Description

Initialize a comprehensive .agent/ folder structure for AI-first development. Use this skill when starting a new project that needs AI agent documentation, session tracking, task management, and coding standards. Generates full structure based on proven patterns from production projects.

# SKILL.md


name: agent-folder-init
description: Initialize a comprehensive .agent/ folder structure for AI-first development. Use this skill when starting a new project that needs AI agent documentation, session tracking, task management, and coding standards. Generates full structure based on proven patterns from production projects.


Agent Folder Init

Create a comprehensive .agent/ folder structure for AI-first development workflows.

Purpose

This skill scaffolds a complete AI agent documentation system including:

  • Session tracking (daily files)
  • Task management
  • Coding standards and rules
  • Architecture decision records
  • Security checklists
  • SOPs for common workflows
  • Agent config folders (.claude, .codex, .cursor) with commands, rules, and agents

When to Use

Use this skill when:

  • Starting a new project that will use AI coding assistants
  • Setting up AI-first development workflows
  • Migrating an existing project to use structured AI documentation

Usage

Run the scaffold script:

python3 ~/.claude/skills/agent-folder-init/scripts/scaffold.py --help

# Basic usage
python3 ~/.claude/skills/agent-folder-init/scripts/scaffold.py \
  --root /path/to/project \
  --name "My Project"

# With custom options
python3 ~/.claude/skills/agent-folder-init/scripts/scaffold.py \
  --root /path/to/project \
  --name "My Project" \
  --tech "nextjs,nestjs" \
  --allow-outside

Generated Structure

Documentation (.agent/)

.agent/
β”œβ”€β”€ README.md                    # Navigation hub
β”œβ”€β”€ SYSTEM/
β”‚   β”œβ”€β”€ README.md
β”‚   β”œβ”€β”€ RULES.md                 # Coding standards
β”‚   β”œβ”€β”€ ARCHITECTURE.md          # What's implemented
β”‚   β”œβ”€β”€ SUMMARY.md               # Current state
β”‚   β”œβ”€β”€ PRD.md                   # Product Requirements Document
β”‚   β”œβ”€β”€ ENTITIES.md              # Entity documentation
β”‚   β”œβ”€β”€ ai/
β”‚   β”‚   β”œβ”€β”€ SESSION-QUICK-START.md
β”‚   β”‚   β”œβ”€β”€ SESSION-DOCUMENTATION-PROTOCOL.md
β”‚   β”‚   └── USER-PREFERENCES.md
β”‚   β”œβ”€β”€ architecture/
β”‚   β”‚   β”œβ”€β”€ DECISIONS.md         # ADRs
β”‚   β”‚   └── PROJECT-MAP.md
β”‚   β”œβ”€β”€ critical/
β”‚   β”‚   β”œβ”€β”€ CRITICAL-NEVER-DO.md
β”‚   β”‚   └── CROSS-PROJECT-RULES.md
β”‚   └── quality/
β”‚       └── SECURITY-CHECKLIST.md
β”œβ”€β”€ TASKS/
β”‚   β”œβ”€β”€ README.md
β”‚   └── INBOX.md
β”œβ”€β”€ SESSIONS/
β”‚   β”œβ”€β”€ README.md
β”‚   └── TEMPLATE.md
β”œβ”€β”€ SOP/
β”‚   └── README.md
β”œβ”€β”€ EXAMPLES/
β”‚   └── README.md
└── FEEDBACK/
    └── README.md

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 library root (e.g., ~/.claude/agents/) to ensure projects get the latest version. Rules are NOT copied because they're inherited from ~/.claude/rules/ at the library/personal level - this prevents duplication and ensures all projects use consistent rules.

Root Files

  • AGENTS.md - Points to .agent/README.md
  • CLAUDE.md - Claude-specific entry point
  • CODEX.md - Codex-specific entry point
  • .editorconfig - Editor configuration

Key Patterns

Naming Conventions

  • Top-level directories: ALL-CAPS (SYSTEM/, TASKS/, SESSIONS/)
  • Files: ALL-CAPS for critical files (README.md, RULES.md), kebab-case for others

Session Files

  • One file per day: YYYY-MM-DD.md
  • Multiple sessions same day use Session 1, Session 2, etc. in the same file

Customization

After scaffolding, customize:

  1. SYSTEM/PRD.md - Fill in your product requirements (use with fullstack-workspace-init)
  2. SYSTEM/ENTITIES.md - Document your data entities
  3. SYSTEM/RULES.md - Add project-specific coding standards
  4. SYSTEM/ARCHITECTURE.md - Document your architecture
  5. SYSTEM/critical/CRITICAL-NEVER-DO.md - Add project-specific violations
  6. SOP/ - Add your standard operating procedures
  7. .claude/rules/ - Add project-specific rules
  8. .claude/commands/ - Add project-specific commands

Integration with Other Skills

This skill integrates with:

Skill How It Works Together
fullstack-workspace-init Use PRD.md to define requirements before scaffolding
linter-formatter-init Sets up quality tooling in the scaffolded project
husky-test-coverage Enforces test coverage in pre-commit hooks

# Supported AI Coding Agents

This skill is compatible with the SKILL.md standard and works with all major AI coding agents:

Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.