jacarty
UserMy template repo for building with Claude
Categories
Indexed Skills (9)
graph-of-thought
Advanced ideation and problem-solving using the Graph of Thoughts (GoT) technique. Use when the user wants deep, interconnected exploration where ideas are combined, refined, and aggregated — not just branched and pruned. Triggers include "graph of thought", "GoT analysis", "combine approaches", "aggregate ideas", "interconnected thinking", "synthesise multiple angles", "cross-pollinate ideas", "merge the best parts", "hybrid solution", or complex challenges where the best answer combines elements from multiple reasoning paths. Also use for systems design, strategy with many interdependencies, multi-stakeholder trade-offs, or wicked problems needing fused partial solutions. Prefer over tree-of-thought when the user wants ideas merged rather than compared and selected.
implementation-spec
Produce a phased implementation spec (build guide) from requirements and research. Use when the user has a researched problem and needs a concrete plan for building it — with phases, acceptance criteria, and file-level change lists. Triggers include "write a spec", "create a build plan", "implementation plan", "how should I build this", "write a PRD", "create a build guide", "phase this work", "break this into steps", "spec this out", or any situation where requirements and research exist and the next step is a structured plan for implementation. Also use when a tracked issue has both requirements and a research brief and needs to move to the build stage.
requirements-elicitation
Structured interview to turn a vague brief or idea into concrete, actionable requirements. Use when the user has a project concept, feature idea, or problem statement that needs sharpening before design or implementation begins. Triggers include "I want to build", "I have an idea for", "help me scope this", "what should the requirements be", "write requirements for", "help me define this project", "what do I need to think about before building", "scope this out", or any situation where the user has intent but not yet a clear specification. Also use when the user shares a brief or PRD that feels incomplete and wants to identify gaps.
research-brief
Investigate a problem, feature, or project idea and produce a structured research brief with findings, recommended approach, and open questions. Use when the user wants to understand the technical landscape before building — comparing libraries, frameworks, patterns, or approaches. Triggers include "research this", "investigate", "what are the options for", "how should I approach", "what tools exist for", "compare approaches to", "do a deep dive on", "technical research for", or any situation where the user needs to gather information and form a recommendation before committing to an implementation path. Also use when a requirements document or tracked issue exists and needs technical investigation before a spec can be written.
trade-off-analysis
Quick, structured comparison of two or three options when a full Tree of Thought exploration would be overkill. Use when the user faces a binary or ternary decision and wants a clear pros/cons/recommendation — not a deep multi-branch exploration. Triggers include "should I use X or Y", "compare these options", "what are the trade-offs", "pros and cons", "which is better", "A vs B", "help me choose between", or any decision with a small number of well-defined alternatives. Prefer this over tree-of-thought when the options are already known and the user wants a decisive recommendation, not an open-ended exploration.
tree-of-thought
Structured ideation and problem-solving using the Tree of Thought (ToT) technique. Use this skill whenever the user wants to brainstorm, ideate, explore solutions to a challenge, solve a complex problem, weigh options, or think through a decision with multiple possible paths. Triggers include phrases like "help me think through", "brainstorm", "explore options", "what are the possible approaches", "ideation session", "problem solve", "tree of thought", "think this through systematically", "explore different angles", "weigh my options", "decision analysis", or any open-ended challenge where multiple solution paths should be explored, evaluated, and refined before arriving at a recommendation. Also use when the user presents a business problem, strategic question, or creative challenge and wants structured exploration rather than a single direct answer.
design-thinking-ideation
Structured design thinking workflow for identifying business opportunities through empathy-driven ideation, prototyping, and test planning. Use this skill whenever the user wants to brainstorm business ideas, identify customer pain points, run a design thinking exercise, generate product concepts, explore unmet needs, or work through the empathise-define-ideate-prototype-test cycle. Triggers include "design thinking", "ideation", "identify opportunities", "customer pain points", "unmet needs", "how might we", "business idea generation", "brainstorm solutions", "prototype an idea", "empathise with users", or any exercise where the user wants to move from understanding a problem to generating and validating solution concepts. Also trigger for strategy or business programme assignments involving design thinking, innovation workshops, or AI-driven solution generation.
value-chain-analysis
Structured Value Chain Analysis using Porter's (1985) framework to identify where and how a firm creates value and competitive advantage through its activities. Use this skill whenever the user wants to analyse how a company creates value, map primary and support activities, identify cost drivers or differentiation sources, find operational improvements, or mentions "value chain", "Porter's value chain", "primary activities", "support activities", "where does the value come from", "how do they make money", "operational analysis", or "activity-based analysis". Also trigger when the user is working on strategy assignments or business programme exercises involving internal activity mapping, cost structure analysis, or identifying sources of competitive advantage at the activity level. Use this skill even when the user doesn't name the framework explicitly but the core question is "where in the business is value created or destroyed?"
vrio-analysis
Structured VRIO framework analysis for evaluating internal resources and capabilities to determine sustainable competitive advantage. Use this skill whenever the user wants to assess whether a resource, capability, or competency provides competitive advantage, or mentions VRIO, resource-based view, internal analysis, competitive advantage assessment, sustainable advantage, or phrases like "is this defensible", "what's our moat", "evaluate our capabilities", "assess our resources", or "competitive positioning of X". Also trigger when the user is working on strategy assignments, MBA/business programme activities, or strategic management exercises that involve internal resource evaluation. Even if the user doesn't name VRIO explicitly, use this skill when the core question is "does this resource/capability give us a lasting edge?"
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.