CaptainCrouton89
- 8 skills
- 0 followers
- 1 day ago last updated
- ▌ Pinning · captaincrouton89Context for the /pin admin workflow — what location pinning is for, how the data flows, and what invariants must not break. Use when working in src/app/pin/, src/app/api/pin/, src/app/api/manual-pin/, scripts/extract-locations.ts, scripts/finalize-locations.ts, data/work-queue.json, data/pinned.json, data/manual-pins.json, or when planning changes that touch lore data, the work queue, pinned coordinates, or free-form manual pins.
- ▌ Headless · captaincrouton89Start/restart the alaria-map-site Next.js dev server (web) in background. Use when starting the dev server, checking status, debugging server issues, or needing to know where logs live.
- ▌ Lore Enrichment · captaincrouton89Enrich an Alaria codex page with specific, reciprocally-linked lore using the page-topic checklist. Walk a page's topics (famous individuals, factions, conflicts/wars, legendary items, locations, historical events, peoples), add named specific detail for the relevant ones, then make every reference two-way — create/update the referenced entity to point back in prose AND wire a codex edge. Use when fleshing out, deepening, or connecting any entity in content/codex/entities/, when building out a domain (e.g. undead), or when the goal is "make the world feel alive / add connective glue."
- ▌
- ▌ Writing Slash Commands · captaincrouton89Create and use custom slash commands to automate Claude Code workflows. Learn argument passing, frontmatter configuration, bash integration, and file references for building reusable prompts.
- ▌ Skills Guide · captaincrouton89Defines required structure, frontmatter format, and best practices for SKILL.md files. Use BEFORE creating or editing any skill - this is the spec to follow, not optional reference.
- ▌ Writing Documentation For Llms · captaincrouton89Teaches how to write effective documentation and instructions for LLMs by assuming competence, using progressive disclosure, prioritizing examples over explanations, and building feedback loops into workflows.
- ▌ Auditing Security · captaincrouton89Identify and remediate vulnerabilities through systematic code analysis. Use when performing security assessments, pre-deployment reviews, compliance validation (OWASP, PCI-DSS, GDPR), investigating known vulnerabilities, or post-incident analysis.