AGENT SKILL

document-directory

Create or update a subdirectory's own CLAUDE.md file after substantial work in that module. Only for app or system documentation tier projects.

License 许可
MIT
最近更新
2026-08-05
Stars
★ 0
Forks
0

01 前言 Front Matter

name
document-directory
description
Create or update a subdirectory's own CLAUDE.md file after substantial work in that module. Only for app or system documentation tier projects.

03 SKILL.md 正文

Document directory

Claude Code loads subdirectory CLAUDE.md files on demand, only when it reads a file in that subtree. Detailed knowledge sits exactly where it's relevant without bloating every session.

When to run

  • Doc tier is app or system. Never for script or tool.
  • After implementation has touched a module substantially enough that a future session would benefit from a summary.

Process

  1. Check for existing subdirectory CLAUDE.md. If one exists, update it with what's new — preserve prior content that's still accurate.

  2. If none exists, create one covering:

    • Purpose and responsibility (1-2 sentences).
    • Key architectural decisions (link to ADRs where they exist).
    • Non-obvious patterns or gotchas a future session would have to rediscover.
    • Do not repeat root CLAUDE.md content — inheritance is automatic.
  3. Keep it short. A subdirectory CLAUDE.md as long as the root file has lost the point. Complex modules get an ADR or dedicated doc linked from a still-short CLAUDE.md.

  4. Commit separately from implementation unless the project's convention says otherwise.

What this skill must never do

  • Never run on script or tool tier projects.
  • Never duplicate root CLAUDE.md content.
  • Never let a subdirectory file grow to root-file length.

04 同仓库更多 Skills

lynchypin
lynchypin/project-onboard

wayfinder

The orchestration hub for all work. Creates a map of investigation tickets (grilling, research, prototype, task, bug), resolves them one at a time with strict grilling discipline, manages risk posture pauses during implementation, and hands off to to-spec when the map is complete. Use for any work regardless of size — a trivial task has a small map, a large migration has many tickets.

★ 0
lynchypin
lynchypin/project-onboard

to-tickets

Break the spec into small, independently-implementable tracer-bullet vertical slices. No checkpoint gate — hands off directly to wayfinder for implementation orchestration.

★ 0
lynchypin
lynchypin/project-onboard

to-spec

Synthesize a specification from the completed wayfinder map. Never runs its own interview — it only writes down what wayfinder's grilling tickets already established, at a depth proportional to the project's documentation tier.

★ 0
lynchypin
lynchypin/project-onboard

tdd

Reference material for test-driven development discipline. Red before green, one slice at a time. Use as reference during implementation, not as a step-by-step procedure.

★ 0
lynchypin
lynchypin/project-onboard

start-session

Orient a new session in any project directory. Detects empty directory, existing codebase, or resume state, gathers cheap signals, and routes to wayfinder. The only user-invoked entry point.

★ 0
lynchypin
lynchypin/project-onboard

setup

Configures the issue tracker. Called by start-session during first orient. Model-invoked — runs automatically as part of the flow, not user-triggered.

★ 0