Claude Skills by TonyLikeDev

Use when the user wants to execute development tasks, work through a phase, implement code, run tests, write documentation, tick off roadmap items, or when the user says "let's build", "start working", "do the next task", "implement", "run the build tasks", or "tick this off".

Map an existing codebase into LAYOUT.md, covering the folder tree with the purpose of each part, the components and how they connect, the database schema, and a list of the business logic with where each piece lives. Use when the user asks to map, document or describe the layout or architecture of an existing project.

Use when the user wants to start a new project, generate a project plan, create a roadmap, scaffold a PLAN.md and ROADMAP.md, or turn a project brief into a structured development plan with phases, tasks, exit criteria, and a live status tracker.

Use when starting a new work session, loading project context, narrowing the context window to the current phase, checking what to work on next, or when the user says "what should I work on", "load my roadmap", "where am I in the project", or "start session".

Plan a new project, from an idea or from existing documents (proposal, spec, design notes, a PDF), or a big addition to an existing project, into PLAN.md. ROADMAP.md is not created until the user approves the plan; then the roadmap is generated and the first action runs. Use when the user asks to plan a new project or a big feature, turn an idea or proposal into a plan, or write a project schedule.

Check ROADMAP.md against the actual code and git history and fix the drift, such as ticked items whose evidence is gone, finished work nobody ticked, and stale next actions or progress. Use when the user comes back after a break or from another machine, or asks whether the roadmap is up to date.

Find copy-pasted code (functions, classes, components, modules, queries), merge each duplicate group into one shared function or component with the differences passed as a variant, and report the before/after line counts. Use when the user runs /dedup-merge or asks to check for duplicated code, merge duplicates, or make copy-pasted code share one implementation.

Map an existing codebase into LAYOUT.md, covering the folder tree with the purpose of each part, the components and how they connect, the database schema, and a list of the business logic with where each piece lives. Use when the user runs /layout-init or asks to map, document or describe the layout or architecture of an existing project.

Routes work between the TrustMeBro skills (layout-init, roadmap-planner, roadmap-sync, dedup-merge) and says which to run next. Use when the request is vague, spans several skills, or the user asks what to do next.

Plan a new project, from an idea or from existing documents (proposal, spec, design notes, a PDF), or a big addition to an existing project, into PLAN.md. ROADMAP.md is not created until the user approves the plan; then the roadmap is generated and the first action runs. Use when the user runs /roadmap-planner or asks to plan a new project or a big feature, turn an idea or proposal into a plan, or write a project schedule.

Check ROADMAP.md against the actual code and git history and fix the drift, such as ticked items whose evidence is gone, finished work nobody ticked, and stale next actions or progress. Use when the user runs /roadmap-sync, comes back after a break or from another machine, or asks whether the roadmap is up to date.

Use when the user wants to execute development tasks, work through a phase, implement code, run tests, write documentation, tick off roadmap items, or when the user says "let's build", "start working", "do the next task", "implement", "run the build tasks", or "tick this off".

Map an existing codebase into LAYOUT.md, covering the folder tree with the purpose of each part, the components and how they connect, the database schema, and a list of the business logic with where each piece lives. Use when the user asks to map, document or describe the layout or architecture of an existing project.

Use when the user wants to start a new project, generate a project plan, create a roadmap, scaffold a PLAN.md and ROADMAP.md, or turn a project brief into a structured development plan with phases, tasks, exit criteria, and a live status tracker.

Use when starting a new work session, loading project context, narrowing the context window to the current phase, checking what to work on next, or when the user says "what should I work on", "load my roadmap", "where am I in the project", or "start session".

Plan a new project, from an idea or from existing documents (proposal, spec, design notes, a PDF), or a big addition to an existing project, into PLAN.md. ROADMAP.md is not created until the user approves the plan; then the roadmap is generated and the first action runs. Use when the user asks to plan a new project or a big feature, turn an idea or proposal into a plan, or write a project schedule.

Check ROADMAP.md against the actual code and git history and fix the drift, such as ticked items whose evidence is gone, finished work nobody ticked, and stale next actions or progress. Use when the user comes back after a break or from another machine, or asks whether the roadmap is up to date.