h14h
@h14h
Public Skills
but-why
by h14h
Collaboratively write, update, or consult a project's WHY.md and design/ conceptual models — the documents that capture purpose, values, priorities, target users, and how users think about the product. Use when the user wants to create project documentation about why their project exists, discuss project vision or values, write a WHY.md, update conceptual models, revisit project priorities, or when you need to understand a project's purpose and values before doing work. Triggers include "but why", "write a WHY", "document the purpose", "update the why", "project vision", "collaborate on why", "update the design", "conceptual model", "what are the project values", "what's the priority", or "use but-why".
now-how
by h14h
Generate, update, or consult a project's HOW.md and domain specs — the architecture map and domain-specific documentation that tells collaborators how the codebase is organized and what they need to know beyond what the code itself shows. Use when the user wants to document the codebase architecture, create or update domain specs, write a HOW.md, map the codebase, keep documentation in sync with code changes, or when you need to understand a project's architecture before answering questions or doing work. Triggers include "now how", "document the architecture", "write specs", "update the docs", "map the codebase", "update the spec for [domain]", "create docs", "how does [X] work in this project", "check the docs first", or "use now-how".