rogerjeasy
UserClaude Code plugin that runs an end-to-end hackathon workflow — Devpost recon, ideation scored against the real judging criteria, architecture, spec-driven build, deploy, and a judge-ready submission package — as 11 gated phases you never have to remember. Node, zero runtime dependencies.
Categories
Indexed Skills (22)
architecture-diagramming
Use at :architect — what judges actually read in an architecture diagram, and the tier model the three emitters render from.
backend-architecture
Use at :architect — FastAPI service structure as Karma (Second Place, Dynatrace) built it, the gateway/agent-service split, secret handling, dependency injection, and error contracts that don't leak internals.
data-modeling
Use at :architect — the twelve-section data-model doc Kintwadi (Best Design) shipped, entity grouping, the RLS policy taxonomy, and how to argue for a database rather than just list its features.
devpost-recon
Use when reading a Devpost hackathon page to extract rules, criteria, deadlines and requirements — covers page anatomy, where requirements actually hide, and what to quote verbatim.
framework-drift-guard
Use when a stack pins a fast-moving framework — generates the "This is NOT the framework you know" banner that stops an agent writing code from stale training data
frontend-architecture
Use at :architect — Next.js App Router structure as Kintwadi (Best Design) built it, protection as the default rather than a per-page opt-in, and where the data-access layer sits.
gherkin-requirements
Use at :requirements — writing scenarios that are executable acceptance tests rather than decorative prose.
judge-ready-readme
The README-as-landing-page structure -- live demo first, why-this-tech placed before any badges table, security model, optional demo-data and disclosure sections
judging-criteria-scoring
Use when turning hackathon judging criteria into a scoring rubric, or when choosing which track to enter — covers Stage-One gating, tiebreak order, bonus headroom and expected value.
monorepo-structure
Use at :stack — choosing between a next-monolith and a multi-service repository shape, with both shapes as measured in winning repositories.
project-description
Use when writing the project description for a hackathon entry — the section spine that survives implementation, named characters as load-bearing, and mapping headings to judging criteria.
security-invariants
Use at :architect — generates the fail-closed, defense-in-depth AGENTS.md invariants contract from the architecture's access-control model, scaled honestly to the project
sponsor-tech-thesis
Use when deciding or writing the one-line justification for a hackathon's required technology — the form it takes, where to place it in a submission, and how to avoid claiming more than the architecture supports.
ui-design-principles
Use at :architect — the design system distilled from 01-design-system.md, the prompt behind Kintwadi's Best Design win, fixed once before the first screen and reused for every screen after.
winning-ideation
Use when generating or evaluating hackathon project ideas — the angles that win, the anti-patterns that lose, and the inversion, demoability and quantification tests.
cicd-github-actions
Path-filtered per-service deploy workflows with keyless WIF/OIDC auth, test-then-deploy ordering
containerization
Per-service, multi-stage Dockerfiles sized for a two-day project, not a production system
demo-runbook
Reproducible walkthroughs -- the Judge Quick-Start (no account required) pattern, idempotent seed and reset, a golden-run fallback for a degrading live environment
demo-video-script
Sub-three-minute video structure -- hook, problem, demo, technical depth, close -- each shot with a timing budget, checked against the platform's own video requirements
deploy-targets
Selection criteria and time-to-first-URL for Vercel, Cloud Run, Railway, Render, AWS, and Docker Compose
devpost-submission
Mapping artifacts to Devpost form fields, organized by the platform's own form steps; the requirements tracker; what the challenges log is for
iac-terraform
Terraform module layout sized for a project with a two-day lifespan, not a production system
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.