Results for “tec”

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

This skill should be used when the user asks to "understand a codebase", "get code context", "research a library", "explore a repository", "find code examples", "look up documentation", asks a natural-language code/technology question (e.g. "how does X work", "X vs Y", "best practice for Z"), or wants to understand how a specific project, library, or concept works before making changes.

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for writing documentation or architectural decision records.

Generate user-friendly "Explain Like I'm 5" feature documentation for end users by reading the codebase. Use this skill whenever the user wants to document a feature for non-technical users, write help docs, create an explainer for a feature in their app, produce onboarding content, or asks "make a user doc for X". Trigger on phrasings like "ELI5 the closeout flow", "write user docs for the kanban view", "explain this feature to a customer", "make a help article for X", "document this for end users". Also known as "E-features-LI5". This skill produces plain-language docs written for someone with the app open trying to get something done — not internal developer docs (use the `teach` skill for those) and not feature announcements.