Trigger for the docs-page-authoring skill: load it before writing or editing a README or any other documentation page, and when a change adds or renames an option, an error, or a supported version.
Author Diagrammer JSON for the Diagrammer viewer. Use whenever the user asks for a mind map, concept map, flowchart, tree, dependency graph, ER diagram, or timeline. Output a single JSON document conforming to the schema below.
116mo agoReviewMountCreate a free account to mount
How to word anything the founder reads or answers - questions, grilling rounds, approvals, decisions, summaries, reports - at the technical level saved in project.toml [owner] level (non-technical, basics or technical). Use before writing any message or document for the founder.
1618d agoReviewMountCreate a free account to mount
Hypothesis-driven debugging protocol — reproduce, isolate, hypothesize, test, fix, document. Apply when debugging a failure. Find the root cause, not a workaround.
Generate and maintain project documentation from the code (README, API reference, architecture notes, setup docs). Re-runnable to keep docs in sync as the code changes.
Block dangerous git commands (push, force push, reset --hard, clean, branch -D, checkout/restore .) and enforce Conventional Commits & Branch Protection before an AI agent runs them. Installs hook scripts for Claude Code, Cursor, Cursor CLI, and Gemini CLI; documents Google Antigravity Terminal deny lists. Use when the user wants git safety hooks, to block git push or destructive git in agents, or to mirror the same policy across AI coding tools.
29211d agoReviewMountCreate a free account to mount
Full expert review protocol. 8-expert, 2-wave deliberation for comprehensive codebase and documentation review. Invoke before major milestones, after shipping feature clusters, or before staging/production deployment.
Full expert review protocol. 8-expert, 2-wave deliberation for comprehensive codebase and documentation review. Invoke before major milestones, after shipping feature clusters, or before staging/production deployment.
Use when designing a database schema, writing migrations, reviewing SQL queries, or choosing between relational and document models — covers naming, index strategy, migration safety, N+1 prevention, and transaction boundaries.
The legal agent's method - read the founder's playbook and the region packs, grade each checklist item GREEN, YELLOW, RED or UNSETTLED with a cited and dated source, draft documents flagged for counsel, escalate. Use at setup, before launches, and on features touching personal data, payments, children, AI output or marketing claims.
1618d agoReviewMountCreate a free account to mount
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page. Do NOT use for URLs ending in .md those are already markdown, use WebFetch directly.
224mo agoReviewMountCreate a free account to mount
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so the result is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says \"STE\", \"Simplified Technical English\", \"ASD-STE100\", \"de-slop\", \"make this readable\", \"write for non-native readers\", or asks for docs that translate well. Enforces the 53 rules of the standard (Issue 9) with a deterministic lint gate.
29211d agoReviewMountCreate a free account to mount
Explain a Microsoft ecosystem concept to someone who is confused by it, after working out what they actually misunderstand. Use when someone asks what something is or why it behaves the way it does across Copilot Studio, Power Platform, Dataverse, Dynamics 365, Microsoft Foundry or Entra - particularly when they have already read the documentation and are still stuck.
Capture architectural decisions that have already been made, as structured ADRs (Architecture Decision Records). Use when user says 'record this decision', 'ADR this', 'why did we choose X', 'document this trade-off', 'we decided to...', or when a choice between alternatives has been settled and needs writing down. This records a decision; it does not make one. A question of the form 'should we use X or Y' is a design discussion, not an ADR request.
An independent second reader for both documents and code - reviews specs, designs, contracts and tickets for gaps and contradictions before they are handed on, and every developer diff for correctness, simplicity and fit to its ticket before it goes to QA. Writes findings and never changes what it reviews, and suggests adding agents to the team when the project or its requirements have grown past the team setup chose. Use on every spec, design and diff before the next hand-off.
1618d agoReviewMountCreate a free account to mount
Use when SEC XBRL company-facts data returns 404, is empty, or has sparse coverage — typical for recent FPIs (foreign private issuers), recent IPOs, SPACs, or shell companies. Defines the document hierarchy and extraction rules to recover shares-outstanding data from filing text when structured XBRL is unavailable.
Rewrite text that reads like a model wrote it into something a person would actually send. Use when a proposal, customer email, README or executive summary reads like a brand deck, when a draft leans on \"seamless\", \"robust\", \"pivotal moment\" or \"evolving landscape\", when every sentence could be pasted into another company's blog post unchanged, when a document hedges instead of taking a position, or when a reviewer says a page is fine but cannot say what it told them.
This rule provides essential guidance for executing GitHub CLI (gh) commands correctly when using the run_terminal_cmd tool. It covers the critical workaround for pager-related issues that cause gh commands to fail with "cannot open '|' for reading" errors. The rule documents why piping gh commands to cat (e.g., gh run list | cat) is necessary and provides templates for common GitHub workflow operations, issue management, and pull request commands. Essential for debugging GitHub Actions workflows and accessing repository information via CLI. This rule should be requested whenever: Working with GitHub CLI commands Debugging GitHub Actions workflows Encountering terminal/pager-related errors with gh commands Need to list workflow runs, view logs, or manage GitHub repository resources via CLI The rule is now saved and ready to be used by agents who need to execute GitHub CLI commands correctly.
3117mo agoReviewMountCreate a free account to mount