Jartan-LLC

How agents, skills, and commands work in Claude Code projects.

GitHub conventions -- branch naming, commit format, issue/PR templates, and safe issue/PR referencing in comments.

API error response format -- machine-readable codes, human-readable reasons, status code rules.

Language-agnostic code hygiene -- honest comments, no dead/reinvented/duplicated code, truthful names, real implementations, and scoped (never blanket) diagnostic suppressions.

Language-agnostic structural craft -- decompose on responsibility not size, prefer deep modules over shallow piles, and shape cohesion, coupling, interfaces, error contracts, and data invariants. Sibling to code-hygiene and readable-code.

Documentation writing conventions -- style, structure, tone, and quality standards.

CSS design system principles -- token usage, semantic layering, mobile-first, component isolation.

Logging conventions -- level usage, formatting style, structured output.

MCP tool error response format — canonical error object, standard codes, retry semantics.

Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.

How agents, skills, and commands work in this project.

Documentation writing conventions — style, structure, tone, and quality standards.

CSS design system principles — token usage, semantic layering, mobile-first, component isolation.

GitHub conventions — branch naming, commit format, issue/PR templates, and safe issue/PR referencing in comments.

Logging conventions — level usage, formatting style, structured output.

Integration test philosophy — test observable behavior, fixture composition, canary markers for library internals.