IdkwhatImD0ing

blog-writer

Write or expand Hackathon Playbook blog posts in `lib/blog.ts` using the site's rich content block system and SEO rules. Use this skill whenever the user asks for a new article, blog idea, SEO post, content update, or anything that should become a `/blog/[slug]` entry, even if they only describe the topic casually.

domain-to-spec

Turn a non-coder's domain expertise into `AGENTS.md` and `PRD.md` at the repo root before scaffolding. Use this skill first for new projects, idea-to-spec work, PRD creation, app planning, or when the user describes a profession, workflow, constraint, or outcome and needs a buildable software blueprint.

quickstart

Orchestrate a new project from idea to running scaffold by chaining `domain-to-spec`, `scaffold-frontend`, and optional `scaffold-backend`. Use this skill when the user wants a one-shot setup, full-stack bootstrap, empty-repo starter, or guided path from rough idea to `AGENTS.md`, `PRD.md`, `client/`, and optionally `server/`.

scaffold-backend

Create a PRD-driven FastAPI backend in `server/` from repo-root `AGENTS.md` and `PRD.md`. Use this skill after frontend scaffolding only when `PRD.md` says `Backend Needed?` is Yes, especially for API routes, Pydantic models, health checks, optional Supabase wiring, and type-safe placeholder data.

scaffold-frontend

Create a PRD-driven Next.js frontend in `client/` from repo-root `AGENTS.md` and `PRD.md`. Use this skill after `domain-to-spec` when the user wants the initial UI scaffold, pages, navigation, types, and optional API client generated from the confirmed PRD.

v0-prompt-crafter

Turn a PRD, product idea, app description, screenshot brief, or rough UI concept into a high-signal Vercel v0 prompt. Use this skill whenever the user wants a v0 prompt, landing page prompt, app UI generation prompt, visual direction, shadcn/Magic UI/Aceternity guidance, or a more distinctive interface than generic AI output.

hackathon-idea-validation

Validate a hackathon idea quickly against real constraints and judging criteria before building. Use when deciding whether a hackathon project idea is worth pursuing.

hackathon-pitch-prep

Prepare a winning hackathon pitch: narrative structure, demo choreography, judge psychology, and Q&A handling. Use when preparing to present a hackathon project.

hackathon-stack-selection

Choose a hackathon tech stack optimized for shipping in 24-48 hours. Use when picking frameworks, hosting, and AI tooling at the start of a hackathon.

hackathon-submission-checklist

Ship a complete hackathon submission: README, demo video, Devpost write-up, and deliverables judges remember. Use when finalizing a hackathon submission.

readme-writer

Write a winner-grade README for a hackathon project: a centered hero with shields.io badges, a clickable demo-video poster, awards and stats tables, a Mermaid architecture diagram, a tech-stack table, a repo map, team cards, and an honest build-context note, then set the repo's About metadata (description, website, and topics) to match. Use this skill whenever the user wants a README, GitHub landing page, project writeup, repo polish, or repo description and tags for a hackathon submission or portfolio piece.

devpost-writer

Write a compelling Devpost project submission for a hackathon: the tagline, the standard story sections (Inspiration, What it does, How we built it, Challenges, Accomplishments, What we learned, What's next), the Built With tags, and the Try it out links. Use this whenever the user is submitting to Devpost, or needs to write or polish a Devpost project story, writeup, or submission.

portfolio-builder

Generate a distinctive, recruiter-facing portfolio website that showcases a hackathon project, even when the project is not a web app (hardware, an ML model, a CLI, or research). Installs and uses Anthropic's frontend-design skill so each project gets a unique, non-templated design, then builds a one-page case study with a hero, problem, architecture, demo, results, team, and honest limits. Use this whenever the user wants a project showcase site, case-study page, portfolio site, or recruiter-facing landing page for what they built.

ship-it

Produce all four post-hackathon deliverables in one pass: the recruiter-facing portfolio site, the GitHub README, the Devpost submission, and the YouTube demo description. Gathers the shared facts once, then runs portfolio-builder, readme-writer, devpost-writer, and youtube-writer in order so the four read as one consistent story. Use this whenever the user wants to ship everything after a hackathon, package a finished project for recruiters, or run the full post-hackathon toolkit at once instead of one skill at a time.

youtube-writer

Write the YouTube title and description for a hackathon project's demo video, tuned for recruiters and search. Use this whenever the user is uploading or has uploaded a demo video and needs the video title or description copy.

bugfix-doctor

Systematic bug-fixing workflow for non-coders. Walks through reproduce, isolate, fix, test, and verify. Explains all errors in plain English. Use when something is broken and the user does not understand why.

demo-prep

Produces a step-by-step live demo script for hackathon presentations. Covers the problem, the app walkthrough, and the outcome. Includes a backup plan. Use before presenting at a hackathon or demo day.

feature-builder

Structured workflow for implementing a new feature when you have no coding experience. Returns a plan, files list, commands, manual test steps, and rollback plan. Use when the user wants to add a feature to their project.

non-coder-mode

Communication and safety guardrails for helping non-coders build software in Cursor, Claude Code, or similar tools. Use this skill whenever the user says they are not technical, asks for plain English, seems unfamiliar with coding, is a domain expert building an app, or needs step-by-step safety rails.