Skip to main content
Run any Skill in Manus
with one click
CaptainCrouton89
GitHub creator profile

CaptainCrouton89

Repository-level view of 29 collected skills across 4 GitHub repositories.

skills collected
29
repositories
4
updated
2026-06-26
repository explorer

Repositories and representative skills

skills-guide
computer-occupations-all-other

Defines 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.

2025-12-11
fixing-bugs-systematically
software-developers

Diagnose and fix bugs through systematic investigation, root cause analysis, and targeted validation. Use when something is broken, errors occur, performance degrades, or unexpected behavior manifests.

2025-11-24
reviewing-code
software-quality-assurance-analysts-and-testers

Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.

2025-11-24
documenting-code
software-developers

Maintain project documentation synchronized with code. Keep feature specs, API contracts, and README current with init-project standards. Use when updating docs after code changes, adding new features, or ensuring documentation completeness.

2025-11-24
investigating-code-patterns
software-developers

Systematically trace code flows, locate implementations, diagnose performance issues, and map system architecture. Use when understanding how existing systems work, researching concepts, exploring code structure, or answering "how/where/why is X implemented?" questions.

2025-11-24
executing-work-in-parallel
computer-occupations-all-other

Coordinate concurrent task execution through agent delegation. Plan independent work, manage dependencies, and execute multiple agents simultaneously. Use when handling multiple unrelated tasks, research investigations, or layer-based implementations that can run concurrently.

2025-11-24
planning-implementation
software-developers

Create structured implementation plans before coding. Use when breaking down complex features, refactors, or system changes. Validates requirements, analyzes codebase impact, and produces actionable task breakdowns with identified dependencies and risks.

2025-11-24
railway-cli-management
network-and-computer-systems-administrators

Deploy, manage services, view logs, and configure Railway infrastructure. Use when deploying to Railway, managing environment variables, viewing deployment logs, scaling services, or managing volumes.

2025-11-24
Showing top 8 of 22 collected skills in this repository.
monster-creation
technical-writers

Author a complete Alaria bestiary creature — canon-integrated lore + at least one outward codex edge + a validated 5e statblock — at Monster-Manual quality, without the convergence/monotony that destroys a bestiary at scale. Carries the anti-slop bar (the one diagnostic: does it hand a GM a live lever this session?) and the anti-convergence rules that are the value-add over plain lore-writing: the death-residue section is OPTIONAL not mandatory, the cinderbound/galebound bound-family litany is banned, resolution beats rotate, CR/role spread is a hard batch gate, naming heads diversify, and a batch passes a read-five-in-a-row gate before it ships. Use when writing any new `content/codex/entities/creature-*.md`, when running or reviewing a batch, or whenever you need the bestiary quality contract in one place. This skill is the front door; the detailed contract is `context/method-taxonomy.md`.

2026-06-26
lore-enrichment
technical-writers

Enrich 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."

2026-06-21
pinning
software-developers

Context 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.

2026-05-23
headless
software-developers

Start/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.

2026-05-03
Showing 4 of 4 repositories
All repositories loaded