Tacuchi Workspace Tools Workspace Guide

Workspace Conventions

These conventions apply whenever you detect workspace markers in the project:

• Directories: docs/, tools/
• Instruction files: AGENTS.md, CLAUDE.md, GEMINI.md
• Numbered files: NNN-*.ext pattern (e.g., 001-arquitectura.md)

If any of these markers exist, follow all conventions below automatically.

1. Where Does This Go?

2. Directory Structure

docs/ — Project documentation

docs/
├── arquitectura/       ← architecture and design (mandatory)
├── planes/             ← work plans and specs
├── decisiones/         ← ADRs (Architecture Decision Records)
├── manuales/           ← installation, configuration, deployment guides
├── especificaciones/   ← functional and technical specs
└── scripts/            ← SQL, analysis scripts, DDL
    ├── ddl/
    └── analisis/

tools/ — Scripts and skills

tools/
├── scripts/            ← executable code (Python, Bash, etc.) + SKILL.md
│   └── <tool-name>/
│       ├── SKILL.md
│       └── 001-script.sh
└── skills/             ← instruction-only (no executable code), SKILL.md only
    └── <skill-name>/
        └── SKILL.md

3. File Numbering

Format: NNN-descriptive-name.ext (3-digit: 001, 002, ...) Before creating a file, check the highest existing number and increment by 1.

4. Rules

• Every tool in tools/scripts/ or tools/skills/ MUST have a SKILL.md with description in frontmatter.
• SKILL.md can also exist inside src/, lib/, etc. when the user requests it.
• Save work plans in docs/planes/NNN-<plan>.md.
• Save architectural decisions in docs/decisiones/NNN-<decision>.md.

5. NEVER Do This

• NEVER create unnumbered files in docs/ — breaks chronological ordering, causes confusion when switching agents
• NEVER put executable code in tools/skills/ — skill discovery treats skills/ as instruction-only; executables won't be found by runners
• NEVER create a SKILL.md without a description in frontmatter — the tool becomes invisible to all agent skill discovery systems
• NEVER duplicate content between the instruction file and docs/ — creates drift; instruction file should only reference docs/
• NEVER create docs/planes/ or docs/decisiones/ during initial setup — they fill on demand; empty dirs clutter the workspace
• NEVER create a numbered file without checking the current highest number (ls docs/<subdir>/ first)
• NEVER use a number already taken — always increment from the highest existing number

6. Existing Tools

Before creating a new tool, check these locations for existing ones:

1. tools/scripts/ — project executable tools
2. tools/skills/ — project instruction skills
3. .agents/skills/ — synced project skills
4. .claude/skills/ — Claude-specific skills
5. .gemini/skills/ — Gemini-specific skills

Do not create duplicates. If a similar tool exists, update it instead.

7. References

When creating a tool, follow references/skill-template.md

For instruction file format, see references/instruction-file-guide.md

8. Related Tools

workspace-setup (initial step)

If the project has a monolithic instruction file (>200 lines from /init), suggest:

The instruction file is large. You can split it into docs/arquitectura/ using workspace-setup: npx skills add tacuchi/workspace-tools@workspace-setup

workspace-update (after creating tools)

After creating tools in tools/scripts/ or tools/skills/, suggest syncing:

New tools created. Sync SKILL.md to .agents/skills/ with: npx workspace-update sync

This makes project tools discoverable by all compatible agents.

Source: Tacuchi/workspace-tools — distributed by TomeVault.