Loading...
Loading...
Found 60 Skills
Document project tools and CLI utilities in docs/define/tools/. Use when documenting internal CLIs, scripts, development tools, or third-party integrations that team members need to understand and use.
Deploy a full AI coding workstation with Claude Code, web UI, headless browser, and 5 AI CLIs in a single Docker container
Help the founder decide what to charge and how to package it: the value metric, the tiers, the free-to-paid line, and finding the actual number. Use when the founder is guessing at a price, priced too cheap and can't change it, is stuck on free vs paid, or believes "developers won't pay" so never charges.
Guide developers through setting up development environments with proper tools, dependencies, and configurations
Use btca (Better Context App) to efficiently query and learn from the bknd backend framework. Use when working with bknd for (1) Understanding data module and schema definitions, (2) Implementing authentication and authorization, (3) Setting up media file handling, (4) Configuring adapters (Node, Cloudflare, etc.), (5) Learning from bknd source code and examples, (6) Debugging bknd-specific issues
Write a developer value proposition that is specific, provable, and free of puffery. Use when the messaging leans on "powerful," "better," "seamless," or "best-in-class," when claims have no proof, or when the same line is supposed to reach both the developer and the buyer.
Verify that a web app change actually works by driving the running app from the inside (DOM, network, routing, console, framework state) instead of screenshots or guessing. Use after any user-facing change, when a fix is claimed but unproven, when a test passes but the UI is broken, or when you need a real verdict rather than "looks right". Also use to install and wire up Reticle in a project that does not have it yet.
Interactive macOS system cleanup for any dev machine. Frees disk space by pruning caches, package managers, unused apps, stale dev artifacts, and more. Discovers what's installed rather than assuming a specific setup. Always consults the user before deleting anything. Use when the user asks to: clean up their Mac, free disk space, remove unused apps, prune caches, clean developer artifacts, or any disk space maintenance task.
Diagnosis and repair guide for errors and failures including CI issues. Activate this guide when users mention something is broken, errors occur, things aren't working, CI failures, build errors, test failures, or pipeline issues. DO NOT use this guide for: successful builds, new feature implementation, or code reviews.
Use when managing development tool versions with Mise. Covers installing tools, version pinning, and replacing language-specific version managers.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Surface @context annotations before editing a file. Shows critical constraints, tradeoffs, and risks sorted by priority. Use when about to modify unfamiliar or complex code, or when the user asks what constraints apply to a file.