tn eklentisi

tn içinde ne var

Eklentinin kendi dosyalarından okunan 18 parça.

tn içindeki beceriler

1. 
   assembledevnomad-byte/techneering

   Use when executing implementation plans with independent tasks in the current session

   4 dosya
   13yıldız
2. 
   inspectdevnomad-byte/techneering

   Use after tn:audit passes, when completing major features, or before merging — dispatches a global cross-task code review covering consistency, architecture, and security (distinct from tn:assemble's per-task review)

   2 dosya
   13yıldız
3. 
   redgreendevnomad-byte/techneering

   Use when implementing any feature or bugfix, before writing implementation code

   2 dosya
   13yıldız
4. 
   auditdevnomad-byte/techneering

   Verify implementation matches change artifacts — dual-layer verification of code vs spec compliance and code vs real requirements. Use after implementation is complete.

   13yıldız
5. 
   blueprintdevnomad-byte/techneering

   Use when you have a spec or requirements for a multi-step task, before touching code

   13yıldız
6. 
   compassdevnomad-byte/techneering

   Use when starting any conversation — establishes how to find and use Techneering skills, requiring skill invocation before ANY response including clarifying questions

   13yıldız
7. 
   craftdevnomad-byte/techneering

   Create distinctive, production-grade frontend interfaces with high design quality. Auto-stacked onto an implementation path when a task involves frontend/UI work — pages, components, layouts, styles, interactions. Also available on demand as tn:craft.

   13yıldız
8. 
   diagnosedevnomad-byte/techneering

   Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

   13yıldız
9. 
   draftdevnomad-byte/techneering

   Propose a new change with all artifacts generated in one step. Use when the user wants to describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

   13yıldız
10. 
    forgedevnomad-byte/techneering

    Implement tasks from a change. Use when the user wants to start or continue implementation of an existing change.

    13yıldız
11. 
    gatedevnomad-byte/techneering

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always

    13yıldız
12. 
    isolatedevnomad-byte/techneering

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification

    13yıldız
13. 
    scoutdevnomad-byte/techneering

    Enter scout mode — a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

    13yıldız
14. 
    shipdevnomad-byte/techneering

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion by presenting structured options for merge, PR, or cleanup

    13yıldız
15. 
    sparkdevnomad-byte/techneering

    You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    13yıldız
16. 
    vaultdevnomad-byte/techneering

    Archive a completed change — delta spec merge and move to archive. Use when the user wants to finalize and archive a completed change.

    13yıldız