Total 58,115 skills
Showing 12 of 58115 skills
Helps a founder build the case for raising prices and the moves that justify it; it drives toward a higher price and does not debate whether to raise. Three gated phases: (1) collect the reality (what you charge, what you promise, who buys) and diagnose which market the price has selected (the $1/$10/$100/$1,000-per-month ladder), the profit stakes (a 10% rise can be ~100% more profit), and whether the low price is strategy or fear, landing on a rough higher target; (2) brainstorm, judgment off, moves that justify a higher price — move up a market rung, price on value created not cost saved, build Love and Utility drivers, differentiate, repackage; (3) select, grilling each move down to a few that are good, strategy-consistent, buildable, and wanted. Load when the user asks how much to raise prices, what it would take to charge more, or why their price feels too low. Do NOT load to set the exact price, write the increase letter, define the ideal customer, or choose among the three pricing strategies.
This skill should be used when the user asks to implement Phaser 4 game code, create or edit scenes, add players, enemies, scoring, collectibles, movement, shooting, animations, input, physics behavior, game objects, or complete gameplay features in TypeScript.
Manage App Store product page promoted purchase slots using the `asc` CLI tool. Use this skill when: (1) Listing slots: "asc promoted-purchases list --app-id ID" (2) Promoting an IAP or subscription: "asc promoted-purchases create --app-id ID (--iap-id ID | --subscription-id ID)" (3) Updating visibility / enabled state: "asc promoted-purchases update --promoted-id ID --visible|--hidden --enabled|--disabled" (4) Deleting a slot: "asc promoted-purchases delete --promoted-id ID" (5) User says "promoted purchase", "promoted IAP", "feature on App Store", "App Store product page promotion", "promoted slot"
Address pull request review comments, conflicts, and CI failures. Use when a PR needs unblocking.
Build well-crafted production procedural meshes in Three.js. Use for complete hard-surface assemblies and humanoid robots, profile extrusion, parameter-curve and spine lofts, pillow panels, exact polygon cuts, inset, revolve, sweep, solidify, bevels and fillets, shell thickness, direct-topology apertures, semantic mesh writers, or diagnosing primitive-built forms, coplanar flicker, loose/non-manifold geometry, detached parts, interpenetration, support, clearance, and swept-envelope defects.
Use when the user wants to design, scaffold, build, or iterate on a video game — including brainstorming new game ideas, planning a gameplay loop, choosing an engine, scaffolding a project, adding features, fixing gameplay bugs, or working on assets. Triggers on phrases like "make a game", "create a [genre] game", "build a [type] game", "I want to make a [genre]", or any session inside a game project directory (has docs/, src/, or an engine config).
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
This skill should be used when the user asks to "add sound", "play music", "audio not working", "add background music", "sound effects", "mute button", "audio sprite", "game audio", "play sound effect", or "music won't play".
Orca orchestration coordinator runbook for orchestrator sessions only: bind the Run created by /orca-tasks, dispatch ready tasks one-worktree-one-branch, drive the task DAG, watchdog check --wait, gate failures, auto-merge green PRs, release workers. Also has a quick path for 1-2 task runs without a plan. Invoke with /orca-orchestrate.
Author procedural planetary bodies in Three.js. Use for spherical terrain, continents, ridges, craters, biome masks, coastlines, material variation, analytic normals, altitude LOD, and bodies that must hold up from orbit through close approach.
Get user sign-off on a set of commits, routing any requested changes through fix-feedback until confirmed, then autosquash resulting fixups. Use before a batch of commits is finalized (pushed, submitted as a PR) whenever the caller wants a human confirmation step first.
Critically examine a task specification against the codebase - structure requirements, identify gaps, reuse opportunities and risks, then challenge it with pointed questions and concerns. Use before planning or implementing a task, or whenever a specification needs scrutiny.