brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
Explorer les Skills
Développement · SKILL.md
knowledge-graph
knowledge-graphBuild, refresh and query a deterministic code knowledge graph to cut orientation-token cost. Triggers: knowledge graph, graphify, code graph, god nodes, orientation cost, map the codebase, what connects, callers of, blast radius.
Independent GitHub snapshot · Automated classification · Original documentation governs
Documentation de la Skill
GitHubname: knowledge-graph description: "Build, refresh and query a deterministic code knowledge graph to cut orientation-token cost. Triggers: knowledge graph, graphify, code graph, god nodes, orientation cost, map the codebase, what connects, callers of, blast radius." allowed-tools: Read, Bash, Grep, Glob kernel: kind: methodology version: 1 side_effects: filesystem confirmation: none
The saving is CONDITIONAL on repo size × tangle, not a fixed multiplier. Measured on real repos: ~5.7x fewer tokens/query on a mid-size service, ~73x on a large interconnected one, ~13% on a tiny library. The graph query cost is ~constant; naive full-corpus cost scales with size — so reduction = corpus ÷ constant. Do the arithmetic on YOUR repo, don't quote a headline.
Hard boundary: the graph helps NAVIGATION, not REASONING. "Design a cache", "why is this slow" get zero lift. It gathers context efficiently; it does not think for the model.