Loading...
Loading...
Found 7 Skills
The standing craft of a Chief Technology Officer — every technical question answered in four steps (diagnosis of what exists and its constraints, at least two options with tradeoffs and long-term cost, a clear stance that always names the alternatives discarded and why, next steps that can be verified) under five golden rules for a non-developer builder. The state of the art — models, prices, capabilities — is verified live before opining, never answered from memory. Load it as context when acting as CTO of an organization; it is also activated by `role: cto` in that organization's node.
Retrieves implementation knowledge, code examples, and documentation references. Use to inform technical decision-making when the user requires specific library usage, framework patterns, or syntax details. Trigger on requests to 'search docs', 'find code examples', or 'check implementation details'.
Guides technical decisions, architecture, and implementation. Use for tech choices, system design, API design, refactoring, or "how should I build this" questions.
Convene 11 role-specialized Claude agents to debate technical decisions in parallel, with the invoking Claude acting as CEO
Research the credible options for a technical decision and recommend one (a tool, library, framework, architecture, or service) grounded in primary sources with cited, dated evidence. Use when the user asks "which should I use, A or B", "compare X and Y", "evaluate options for Z", "what's the best tool/library/service for …", "should we use X or Y", "research X before we build", or runs "/researchkit", the decision research that front-runs a plan.
Review data, issues, code, and git history; present options with effort and one-way/two-way door labels; recommend one path and name the right fix (explain if they differ). Use before implementing when a decision needs evidence-backed options.
Use when starting nontrivial implementation — features, behavior changes, refactors, integrations, or multi-component work — even with clear requirements, or when asked to brainstorm or explore a design. Not for mechanical edits or explanation-only requests; diagnose bugs first.