Guide

Decide the demo before the architecture.

The expensive decision at a hackathon is what to build. CrafterWIKI makes it against the judging reality of your event, and only then turns to stack and system design.

The demo-first method

Recon
Rubric → judging lenses and weights, judge backgrounds, prizes and stackable sponsor lanes, constraints, and what the last edition produced.
Patterns
Event brief, winning mechanisms for this kind of event, and similar situations from other events.
Problems → angles
At least six real problems, then three structurally different angles, each with a one-sentence idea, a named live demo moment, human stakes and the mechanisms it bets on.
Judge panelGate
Simulated judges score every angle against the rubric and check whether it has been done before. Kill, merge or keep.
Demo script and pitch
A 2–3 minute storyline with a fallback for every live moment.
Your approvalGate
No stack or architecture decisions until you approve the angle and the demo.
Architecture
Only the system the demo path needs; everything else is a slide.
Build plan
Roles in parallel from hour one, single-device bottlenecks, code freeze, two rehearsals, sleep.

Create a brief →

See a real run: NASA Space Apps 2026

Reading the labels

Grand winner · Podium · Award winner · Runner-up · Finalist: Organizer-confirmed placements. Only these count as wins.
Public vote: Ranked by community voting, with votes stored. Not a jury result.
Featured: Showcased by the organizer without a stated placement.
Reported · unverified: Claimed by a team member or a secondary source; official results not found.
Submitted: On a submission or voting list. Used for base rates, never as a winner.

organizer stated: Written by the organizer or judges: a results post or prize citation.
team stated: Written by the team: project page, README or write-up.
curator inference: CrafterWIKI's own reading of the evidence. Always labelled.
Roster coverage: Only full rosters produce base rates. Partial and winners-only counts are never presented as what an event produced.

Use it from Claude Code

The repository is a Claude Code plugin: a /hack-plan command, four skills, four agents and an MCP server. Load it for one session:

claude --plugin-dir /path/to/CrafterWIKI

Then run /hack-plan <event URL or slug>. Each phase writes hack-plan/<event>/01-recon.md … 06-build-plan.md.

CLI

node cli/crafterwiki.mjs event nasa-space-apps-2026
node cli/crafterwiki.mjs patterns --event-kind agency-open-data-challenge
node cli/crafterwiki.mjs similar --mechanism expert-data-for-everyone --lens scientific-validity
node cli/crafterwiki.mjs search "voice agent" --winners --json
node cli/crafterwiki.mjs deal --mechanism familiar-thing-new-job --seed 7

Node 20 or newer, no install step. Every command accepts --json.

MCP server

A zero-dependency stdio server with the tools search_projects, similar_situations,event_brief, patterns, deal, get_record,list_hackathons and list_facets.

claude mcp add crafterwiki -- node /path/to/CrafterWIKI/mcp/server.mjs

{
  "mcpServers": {
    "crafterwiki": { "command": "node", "args": ["/path/to/CrafterWIKI/mcp/server.mjs"] }
  }
}

Static API

Endpoint	What
`/api/v0/manifest.json`	Version, counts, endpoint list
`/api/v0/index.json`	Every public project and roster entry as a flat item
`/api/v0/taxonomy.json`	Allowed facet values with definitions
`/api/v0/patterns.json`	Winner frequencies and per-event saturation
`/api/v0/hackathons/nasa-space-apps-2025.json`	One event: rubric, prizes, roster, sources
`/api/v0/projects/centinela.json`	One analyzed project with basis-labelled claims

Corrections, additions and removal

Records come from primary sources: organizer results, event pages and team project pages. If a placement is wrong, a source is missing, or you want your project removed, open an issue in the CrafterWIKI repository with the record slug. Removal requests are honored.

To add an event, follow the wiki-curate skill: new facet values go into the taxonomy first, every claim carries a basis, and crafterwiki validate must pass.