c9:T3095,--- name: thermo-nuclear-code-quality-review description: Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review. disable-model-invocation: true --- # Thermo-Nuclear Code Quality Review Use this skill for an unusually strict review focused on implementation quality, maintainability, abstraction quality, and codebase health. Above all, this skill should push the reviewer to be **ambitious** about code structure. Do not merely identify local cleanup opportunities. Actively search for "code judo" moves: restructurings that preserve behavior while making the implementation dramatically simpler, smaller, more direct, and more elegant. ## Core Prompt Start from this baseline: > Perform a deep code quality audit of the current branch's changes. > Rethink how to structure / implement the changes to meaningfully improve code quality without impacting behavior. > Work to improve abstractions, modularity, reduce Spaghetti code, improve succinctness and legibility. > Be ambitious, if there is a clear path to improving the implementation that involves restructuring some of the codebase, go for it. > Be extremely thorough and rigorous. Measure twice, cut once. ## Non-Negotiable Additional Standards Apply the baseline prompt above, plus these explicit review rules: 0. **Be ambitious about structural simplification.** - Do not stop at "this could be a bit cleaner." - Look for opportunities to reframe the change so that whole branches, helpers, modes, conditionals, or layers disappear entirely. - Prefer the solution that makes the code feel inevitable in hindsight. - Assume there is often a "code judo" move available: a re-organization that uses the existing architecture more effectively and makes the change dramatically simpler and more elegant. - If you see a path to delete complexity rather than rearrange it, push hard for that path. 1. **Do not let a PR push a file from under 1k lines to over 1k lines without a very strong reason.** - Treat this as a strong code-quality smell by default. - Prefer extracting helpers, subcomponents, modules, or local abstractions instead of letting a file sprawl past 1000 lines. - If the diff crosses that threshold, explicitly ask whether the code should be decomposed first. - Only waive this if there is a compelling structural reason and the resulting file is still clearly organized. 2. **Do not allow random spaghetti growth in existing code.** - Be highly suspicious of new ad-hoc conditionals, scattered special cases, or one-off branches inserted into unrelated flows. - If a change adds "weird if statements in random places", treat that as a design problem, not a stylistic nit. - Prefer pushing the logic into a dedicated abstraction, helper, state machine, policy object, or separate module instead of tangling an existing path. - Call out changes that make the surrounding code harder to reason about, even if they technically work. 3. **Bias toward cleaning the design, not just accepting working code.** - If behavior can stay the same while the structure becomes meaningfully cleaner, push for the cleaner version. - Do not rubber-stamp "it works" implementations that leave the codebase messier. - Strongly prefer simplifications that remove moving pieces altogether over refactors that merely spread the same complexity around. 4. **Prefer direct, boring, maintainable code over hacky or magical code.** - Treat brittle, ad-hoc, or "magic" behavior as a code-quality problem. - Be skeptical of generic mechanisms that hide simple data-shape assumptions. - Flag thin abstractions, identity wrappers, or pass-through helpers that add indirection without buying clarity. 5. **Push hard on type and boundary cleanliness when they affect maintainability.** - Question unnecessary optionality, `unknown`, `any`, or cast-heavy code when a clearer type boundary could exist. - Prefer explicit typed models or shared contracts over loosely-shaped ad-hoc objects. - If a branch relies on silent fallback to paper over an unclear invariant, ask whether the boundary should be made explicit instead. 6. **Keep logic in the canonical layer and reuse existing helpers.** - Call out feature logic leaking into shared paths or implementation details leaking through APIs. - Prefer existing canonical utilities/helpers over bespoke one-offs. - Push code toward the right package, service, or module instead of normalizing architectural drift. 7. **Treat unnecessary sequential orchestration and non-atomic updates as design smells when the cleaner structure is obvious.** - If independent work is serialized for no good reason, ask whether the flow should run in parallel instead. - If related updates can leave state half-applied, push for a more atomic structure. - Do not over-index on micro-optimizations, but do flag avoidable orchestration complexity that makes the implementation more brittle. ## Primary Review Questions For every meaningful change, ask: - Is there a "code judo" move that would make this dramatically simpler? - Can this change be reframed so fewer concepts, branches, or helper layers are needed? - Does this improve or worsen the local architecture? - Did the diff add branching complexity where a better abstraction should exist? - Did a previously cohesive module become more coupled, more stateful, or harder to scan? - Is this logic living in the right file and layer? - Did this change enlarge a file or component past a healthy size boundary? - Are there repeated conditionals that signal a missing model or missing helper? - Is the implementation direct and legible, or does it rely on special cases and incidental control flow? - Is this abstraction actually earning its keep, or is it just a wrapper? - Did the diff introduce casts, optionality, or ad-hoc object shapes that obscure the real invariant? - Is this logic living in the canonical layer, or did the diff leak details across a boundary? - Is this orchestration more sequential or less atomic than it needs to be? ## What to Flag Aggressively Escalate findings when you see: - A complicated implementation where a cleaner reframing could delete whole categories of complexity. - Refactors that move code around but fail to reduce the number of concepts a reader must hold in their head. - A file crossing 1000 lines due to the PR, especially if the new code could be split out. - New conditionals bolted onto unrelated code paths. - One-off booleans, nullable modes, or flags that complicate existing control flow. - Feature-specific logic leaking into general-purpose modules. - Generic "magic" handling that hides simple structure and makes the code harder to reason about. - Thin wrappers or identity abstractions that add indirection without simplifying anything. - Unnecessary casts, `any`, `unknown`, or optional params that muddy the real contract. - Copy-pasted logic instead of extracted helpers. - Narrow edge-case handling implemented in the middle of an already busy function. - Refactors that technically pass tests but make the code less modular or less readable. - "Temporary" branching that is likely to become permanent debt. - Bespoke helpers where the codebase already has a canonical utility for the job. - Logic added in the wrong layer/package when it should live somewhere more central. - Sequential async flow where obviously independent work could stay simpler and clearer with parallel execution. - Partial-update logic that leaves state less atomic than necessary. ## Preferred Remedies When you identify a code-quality problem, prefer suggestions like: - Delete a whole layer of indirection rather than polishing it. - Reframe the state model so conditionals disappear instead of getting centralized. - Change the ownership boundary so the feature becomes a natural extension of an existing abstraction. - Turn special-case logic into a simpler default flow with fewer exceptions. - Extract a helper or pure function. - Split a large file into smaller focused modules. - Move feature-specific logic behind a dedicated abstraction. - Replace condition chains with a typed model or explicit dispatcher. - Separate orchestration from business logic. - Collapse duplicate branches into a single clearer flow. - Delete wrappers that do not meaningfully clarify the API. - Reuse the existing canonical helper instead of introducing a near-duplicate. - Make type boundaries more explicit so the control flow gets simpler. - Move the logic to the package/module/layer that already owns the concept. - Parallelize independent work when that also simplifies the orchestration. - Restructure related updates into a more atomic flow when partial state would be harder to reason about. Do not be satisfied with "maybe rename this" feedback when the real issue is structural. Do not be satisfied with a merely cleaner version of the same messy idea if there is a plausible path to a much simpler idea. ## Review Tone Be direct, serious, and demanding about quality. Do not be rude, but do not soften major maintainability issues into mild suggestions. If the code is making the codebase messier, say so clearly. If the implementation missed an opportunity for a dramatic simplification, say that clearly too. Good phrases: - `this pushes the file past 1k lines. can we decompose this first?` - `this adds another special-case branch into an already busy flow. can we move this behind its own abstraction?` - `this works, but it makes the surrounding code more spaghetti. let's keep the behavior and restructure the implementation.` - `this feels like feature logic leaking into a shared path. can we isolate it?` - `this abstraction seems unnecessary. can we just keep the direct flow?` - `why does this need a cast / optional here? can we make the boundary more explicit instead?` - `this looks like a bespoke helper for something we already have elsewhere. can we reuse the canonical one?` - `i think there's a code-judo move here that makes this much simpler. can we reframe this so these branches disappear?` - `this refactor moves complexity around, but doesn't really delete it. is there a way to make the model itself simpler?` ## Output Expectations Prioritize findings in this order: 1. Structural code-quality regressions 2. Missed opportunities for dramatic simplification / code-judo restructuring 3. Spaghetti / branching complexity increases 4. Boundary / abstraction / type-contract problems that make the code harder to reason about 5. File-size and decomposition concerns 6. Modularity and abstraction issues 7. Legibility and maintainability concerns Do not flood the review with low-value nits if there are larger structural issues. Prefer a smaller number of high-conviction comments over a long list of cosmetic notes. ## Approval Bar Do not approve merely because behavior seems correct. The bar for approval is: - no clear structural regression - no obvious missed opportunity to make the implementation dramatically simpler when such a path is visible - no unjustified file-size explosion - no obvious spaghetti-growth from special-case branching - no obviously hacky or magical abstraction that makes the code harder to reason about - no unnecessary wrapper/cast/optionality churn obscuring the real design - no clear architecture-boundary leak or avoidable canonical-helper duplication - no missed opportunity for an obvious decomposition that would materially improve maintainability Treat these as presumptive blockers unless the author can justify them clearly: - the PR preserves a lot of incidental complexity when there is a plausible code-judo move that would delete it - the PR pushes a file from below 1000 lines to above 1000 lines - the PR adds ad-hoc branching that makes an existing flow more tangled - the PR solves a local problem by scattering feature checks across shared code - the PR adds an unnecessary abstraction, wrapper, or cast-heavy contract that makes the design more indirect - the PR duplicates an existing helper or puts logic in the wrong layer when there is a clear canonical home If those conditions are not met, leave explicit, actionable feedback and push for a cleaner decomposition. ca:T1075,# Thermo Nuclear Review Use this skill for a comprehensive security and correctness audit of a checked-out branch. ## Prompt You are a security expert performing a comprehensive review of a checked out branch. Audit this branch and its changes extremely thoroughly for bugs, changes that break existing features/functionality, and security vulnerabilities. Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through. # Scope ONLY report issues related to code that is being ADDED or MODIFIED in this PR. Focus on changes in the diff. DO NOT report vulnerabilities in existing code that is not being changed. # Guidelines ## Breaking Functionality Guidelines This is a complex codebase, with many cross-package/module dependencies. Often simple code changes in one place have subtle interactions that break functionality elsewhere. You MUST be extremely thorough in tracing through possible side effects of the changes. ## Breaking Devex Guidelines It can be easy to break developers' ability to run / build the code locally. You MUST catch changes that will impact users' developer experience. Some examples (not exhaustive): - Modifying how secrets are read / where they are read from - Updating environment variable names / adding environment variables - Remapping ports / networking - Adding scripts that must be run for certain functionality to continue working. Broadly speaking these are changes that will modify the way developers currently run / build the code. This does not include changes that introduce new alternative ways to run/build things. Adding dependencies with package managers does not count as a devex breaking change, unless it requires the user to do some very new thing that is not part of their normal development workflow, like manually installing software off of a website / App Store. ## Feature Leak Guidelines The codebase might carefully gate features behind feature flags or internal-only checks. You MUST NOT allow any features that are meant to be behind a feature gate leak. These leaks are often subtle. Be VERY careful and thorough. ## Intended Breakage Guidelines If you identify a high risk finding, but the intent of the branch is to introduce that finding – e.g. break some functionality, remove a feature flag, remove a safeguard – AND the scope of the change is well constrained, you SHOULD NOT waste the author's time by reporting the issue to them. However, if you believe it is likely that they are not aware of the full implications of their change, or you are worried that they are under-weighting the negative impacts (extreme example: a developer pushes a PR titled "Delete the database"), or you are worried that the change is actually malicious, you should still report the finding. ## Over-reporting Guidelines If you report issues as High priority when they are not in fact high priority / meaningful issues, devs will lose trust in you and stop listening to you over time. NEVER misreport the priority / importance of issues. Be extremely thorough in tracing issues end-to-end to gain complete, and total confidence before reporting. # Final Response IF you have medium-to-high priority / risk findings, and there is a PR for this branch, then check the PR/MR discussion using gh/glab cli to see if there are comments from BugBot or others present. If so, take their findings into account. If they found issues you missed, evaluate them to determine if they are valid and include them in your report. If they found some of the same issues you did, see if there is anything from their findings that are worth incorporating into your response. Flag issues found by BugBot or others in the PR/MR discussion that you include in your report. # Critical Rules - NEVER present issues with unfinished research. E.g. Never say something like, "The client has issue X, but if handled in the backend then this is ok." if you have access to the backend code and can check for yourself. - You MUST wait to check the PR/MR discussion until AFTER you have performed your audit. This way you have fresh eyes while you review. - Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.cb:T11c3,--- name: thermo-nuclear-review description: Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks. disable-model-invocation: true --- # Thermo Nuclear Review Use this skill for a comprehensive security and correctness audit of a checked-out branch. ## Prompt You are a security expert performing a comprehensive review of a checked out branch. Audit this branch and its changes extremely thoroughly for bugs, changes that break existing features/functionality, and security vulnerabilities. Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through. # Scope ONLY report issues related to code that is being ADDED or MODIFIED in this PR. Focus on changes in the diff. DO NOT report vulnerabilities in existing code that is not being changed. # Guidelines ## Breaking Functionality Guidelines This is a complex codebase, with many cross-package/module dependencies. Often simple code changes in one place have subtle interactions that break functionality elsewhere. You MUST be extremely thorough in tracing through possible side effects of the changes. ## Breaking Devex Guidelines It can be easy to break developers' ability to run / build the code locally. You MUST catch changes that will impact users' developer experience. Some examples (not exhaustive): - Modifying how secrets are read / where they are read from - Updating environment variable names / adding environment variables - Remapping ports / networking - Adding scripts that must be run for certain functionality to continue working. Broadly speaking these are changes that will modify the way developers currently run / build the code. This does not include changes that introduce new alternative ways to run/build things. Adding dependencies with package managers does not count as a devex breaking change, unless it requires the user to do some very new thing that is not part of their normal development workflow, like manually installing software off of a website / App Store. ## Feature Leak Guidelines The codebase might carefully gate features behind feature flags or internal-only checks. You MUST NOT allow any features that are meant to be behind a feature gate leak. These leaks are often subtle. Be VERY careful and thorough. ## Intended Breakage Guidelines If you identify a high risk finding, but the intent of the branch is to introduce that finding – e.g. break some functionality, remove a feature flag, remove a safeguard – AND the scope of the change is well constrained, you SHOULD NOT waste the author's time by reporting the issue to them. However, if you believe it is likely that they are not aware of the full implications of their change, or you are worried that they are under-weighting the negative impacts (extreme example: a developer pushes a PR titled "Delete the database"), or you are worried that the change is actually malicious, you should still report the finding. ## Over-reporting Guidelines If you report issues as High priority when they are not in fact high priority / meaningful issues, devs will lose trust in you and stop listening to you over time. NEVER misreport the priority / importance of issues. Be extremely thorough in tracing issues end-to-end to gain complete, and total confidence before reporting. # Final Response IF you have medium-to-high priority / risk findings, and there is a PR for this branch, then check the PR/MR discussion using gh/glab cli to see if there are comments from BugBot or others present. If so, take their findings into account. If they found issues you missed, evaluate them to determine if they are valid and include them in your report. If they found some of the same issues you did, see if there is anything from their findings that are worth incorporating into your response. Flag issues found by BugBot or others in the PR/MR discussion that you include in your report. # Critical Rules - NEVER present issues with unfinished research. E.g. Never say something like, "The client has issue X, but if handled in the backend then this is ok." if you have access to the backend code and can check for yourself. - You MUST wait to check the PR/MR discussion until AFTER you have performed your audit. This way you have fresh eyes while you review. - Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through. cc:T4fd,# Thermos Run the two thermo review passes as async background subagents in parallel, then synthesize their results. ## Workflow 1. Determine the review scope from the user request, PR, current branch, or relevant changed files. 2. Gather the diff and any file/context excerpts needed for reviewers to evaluate the change without guessing. 3. Launch both subagents in the same message with `run_in_background: true`: - `subagent_type: "thermo-nuclear-review-subagent"` for bugs, breakages, security, devex regressions, feature-flag leaks, and other branch-audit risks. - `subagent_type: "thermo-nuclear-code-quality-review-subagent"` for maintainability, structure, file-size growth, spaghetti, abstractions, and codebase-health risks. 4. Pass each subagent the same scoped diff/file context and ask it to return prioritized findings with file references and evidence. 5. After both finish, synthesize the results with findings first, deduplicated across reviewers. Weight overlapping findings more heavily, resolve disagreements with your own judgment, and keep summaries brief. If individual background summaries are already visible to the user, do not restate them wholesale. Surface the unified verdict, the highest-signal findings, and any remaining uncertainty.cd:T5fc,--- name: thermos description: "Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits." disable-model-invocation: true --- # Thermos Run the two thermo review passes as async background subagents in parallel, then synthesize their results. ## Workflow 1. Determine the review scope from the user request, PR, current branch, or relevant changed files. 2. Gather the diff and any file/context excerpts needed for reviewers to evaluate the change without guessing. 3. Launch both subagents in the same message with `run_in_background: true`: - `subagent_type: "thermo-nuclear-review-subagent"` for bugs, breakages, security, devex regressions, feature-flag leaks, and other branch-audit risks. - `subagent_type: "thermo-nuclear-code-quality-review-subagent"` for maintainability, structure, file-size growth, spaghetti, abstractions, and codebase-health risks. 4. Pass each subagent the same scoped diff/file context and ask it to return prioritized findings with file references and evidence. 5. After both finish, synthesize the results with findings first, deduplicated across reviewers. Weight overlapping findings more heavily, resolve disagreements with your own judgment, and keep summaries brief. If individual background summaries are already visible to the user, do not restate them wholesale. Surface the unified verdict, the highest-signal findings, and any remaining uncertainty. 5:["$","$L10",null,{"initialTab":"library","templates":[{"id":"express-sql-schema","title":"Database Schema & Query Generator","description":"Design normalized SQL tables, Prisma schemas, indexes, and complex analytical queries.","category":"architecture","tags":["SQL","Prisma","PostgreSQL","Database Design"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"gpt-5-6-sol","promptText":"You are a Senior Database Administrator and Schema Designer.\n\n### Domain Requirement:\n{{domain_requirements}}\n\n### Database Engine:\n{{db_type}}\n\n### Output Needed:\n1. Fully normalized SQL DDL schema (CREATE TABLE statements with PK, FK, and constraints).\n2. Recommended indexes for fast query lookup.\n3. Sample query demonstrating: {{sample_query_task}}.","variables":{"domain_requirements":"E-commerce platform with Users, Orders, OrderItems, Products, and PaymentLogs","db_type":"PostgreSQL / Prisma ORM","sample_query_task":"Top 5 spending customers over the last 30 days with total order counts"},"quickTips":["Generates clean SQL tables with proper foreign key cascades and indexes."]},{"id":"express-mermaid-architecture","title":"Mermaid.js System Architecture Diagram","description":"Generate interactive Mermaid.js flowcharts, sequence diagrams, or entity relationship maps.","category":"architecture","tags":["Mermaid.js","Architecture","Diagram","System Design"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"claude-5-sonnet","promptText":"Act as a Principal System Architect. Generate a valid Mermaid.js diagram for: {{system_description}}.\n\n### Diagram Type:\n{{diagram_type}}\n\n### Requirements:\n- Use clean node labels and proper syntax (no unescaped special characters).\n- Include subgraphs for client tier, API gateway, microservices, database, and background queues.\n- Provide a brief 3-sentence architectural walkthrough following the diagram code block.","variables":{"system_description":"E-commerce checkout pipeline with Stripe webhooks, Redis queue, and Inventory service","diagram_type":"Flowchart (graph TD) or Sequence Diagram"},"quickTips":["Generates syntax-checked Mermaid diagrams ready for GitHub/Notion."]},{"id":"express-docker-setup","title":"Production Dockerfile & Multi-Stage Build","description":"Create ultra-small, secure Docker container configurations with caching and unprivileged users.","category":"architecture","tags":["Docker","DevOps","CI/CD","Containers"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"claude-5-sonnet","promptText":"Act as a Senior DevOps Engineer. Write a production-grade, multi-stage `Dockerfile` and `docker-compose.yml` for a {{app_stack}} application.\n\n### Objectives:\n1. Multi-stage build (deps, builder, runner) to minimize image footprint under 150MB.\n2. Non-root user execution (`USER node` or `USER appuser`) for container security.\n3. Layer caching optimization for fast rebuilds.\n4. Health check endpoint monitoring.","variables":{"app_stack":"Next.js 15 App Router (Standalone Output)"},"quickTips":["Produces production Docker images with non-root security compliance."]},{"id":"express-api-designer","title":"REST / GraphQL API Endpoint Architect","description":"Design production-grade API endpoints with validation schemas, status codes, and security.","category":"architecture","tags":["API","Backend","JSON Schema","REST","Security"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"gpt-5-6-sol","promptText":"Act as a Lead API Architect. Design a production-ready API endpoint for: {{feature_description}}.\n\n### Requirements:\n- Target Stack: {{tech_stack}}\n- Authentication & Security: Bearer JWT validation, rate-limiting, and input sanitization.\n- Response Standards: Standardized JSON envelope with success, data, and error fields.\n\n### Deliverables:\n1. Endpoint definition (HTTP Method, Route path, Query/Body parameters).\n2. Request/Response TypeScript interfaces.\n3. Complete implementation handler code.","variables":{"feature_description":"User profile update with avatar image URL validation","tech_stack":"Next.js App Router (Route Handlers) + Zod"},"quickTips":["Great for bootstrapping secure backend services.","Produces copy-paste Zod schemas."]},{"id":"express-react-hook-builder","title":"Custom Production React Hook Architect","description":"Build robust, typed custom React hooks with loading state, cancellation, and error boundary handling.","category":"coding","tags":["React","Custom Hook","TypeScript","State Management"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"claude-5-sonnet","promptText":"Act as a Principal Frontend Engineer. Create a custom React hook named `{{hook_name}}` for: {{hook_objective}}.\n\n### Tech Stack:\n- React 19 / Next.js App Router\n- TypeScript (Strict Mode)\n\n### Requirements:\n1. Include state for data, loading, error, and refetch capability.\n2. Handle cleanup logic (AbortController for pending network requests or event listeners).\n3. Provide explicit TSDoc type definitions for parameters and return values.\n\n### Output Deliverable:\nProvide the complete hook implementation file and a 5-line usage component example.","variables":{"hook_name":"useDebouncedFetch","hook_objective":"Debounce search queries with cancellation and cache invalidation"},"quickTips":["Produces battle-tested React hooks with AbortController cancellation."]},{"id":"grok-live-api-integration-scaffold","title":"Grok Live API & Real-Time Stream Integrator","description":"Scaffold resilient, production-ready streaming API integrations with tool calling and SSE event handling for Grok 4.6.","category":"coding","tags":["Grok","Live Stream","Real-Time API","WebSockets","xAI","Tool Calling"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"grok-4-6","promptText":"$11","variables":{"api_service_or_stream":"xAI Grok API streaming endpoint with live tool execution","language_and_framework":"TypeScript / Next.js App Router route handlers with Server-Sent Events (SSE)","resilience_strategy":"Exponential backoff retry, abort controller signal propagation, and structured streaming fallback"},"quickTips":["Supports live Server-Sent Events (SSE), typed schema validation, and robust error recovery."]},{"id":"express-type-guard-gen","title":"TypeScript Type Guard & Zod Schema","description":"Generate strict TypeScript type guards and Zod validation schemas for unknown API payloads.","category":"coding","tags":["TypeScript","Zod","Type Guard","Validation"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"gpt-5-6-terra","promptText":"You are a TypeScript Type System Specialist. Generate a strict Zod schema and corresponding Type Guard function for the following data structure:\n\n### Raw JSON Sample / Spec:\n```json\n{{json_sample}}\n```\n\n### Requirements:\n1. Define the Zod schema (`{{schema_name}}Schema`).\n2. Infer the TypeScript type (`export type {{schema_name}} = z.infer`).\n3. Create a type-guard function (`is{{schema_name}}(data: unknown): data is {{schema_name}}`).\n4. Validate edge cases (optional fields, nullable properties, nested arrays).","variables":{"json_sample":"{ \"id\": \"user_123\", \"email\": \"dev@example.com\", \"roles\": [\"admin\"], \"metadata\": { \"lastLogin\": \"2026-08-07\" } }","schema_name":"UserProfile"},"quickTips":["Converts raw API payloads into type-safe Zod schemas."]},{"id":"astra-browser-qa-operator","title":"Astra browser operator with frontend QA checks","description":"End-to-end computer-use brief that builds a page then verifies it in the browser.","category":"computer-use","tags":["GPT-6 Astra","Computer Use","Browser QA","OSWorld"],"authorName":"KingPrompt","authorUrl":"$undefined","targetModel":"gpt-6-astra","promptText":"You are a GPT-6 Astra computer-use operator.\n\n## Goal\n{{goal}} in {{app_url}}.\n\n## Working notes (preserve across windows)\n- App URL: {{app_url}}\n- Verified facts so far: none yet; append each confirmed observation here.\n\n## Rules\n- Prefer fewer, reliable tool calls over exhaustive exploration.\n- Verify visual state after each risky action (screenshot before destructive steps).\n- Narrate progress briefly between tool calls.\n\n## Completion criteria\nContinue until {{done_when}}. Stop only when acceptance checks pass, then summarize what was verified.","variables":{"goal":"Fill out the signup form and verify the confirmation screen","app_url":"https://example.com/signup","done_when":"Confirmation screen visible with no console errors"},"quickTips":["Define completion explicitly; Astra stops early without a stop condition.","Keep working notes short so later windows reuse them without re-derivation."]},{"id":"grok-realtime-trend-sentiment-radar","title":"Grok Real-Time Trend & Sentiment Radar","description":"Leverage Grok 4.6's live real-time stream to analyze trending topics, sentiment velocity, and contrarian perspectives.","category":"data-analysis","tags":["Grok","Real-Time Data","Market Intelligence","Social Velocity","Trend Analysis"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"grok-4-6","promptText":"$12","variables":{"search_topic_or_keyword":"PostgreSQL pgvector vs Dedicated Vector Databases performance benchmarks","timeframe":"Past 7 days live updates","counter_narrative_check":"Examine developer skepticism, production failure modes, and real cost discrepancies"},"quickTips":["Take advantage of Grok's direct access to real-time discussions, technical releases, and market shifts.","Generates both consensus views and contrarian reality checks."]},{"id":"express-etl-pandas","title":"Pandas / Data Transformation Pipeline","description":"Clean, normalize, deduplicate, and aggregate raw datasets using Python Pandas or PySpark.","category":"data-analysis","tags":["Python","Pandas","Data Science","ETL"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"deepseek-v4-pro","promptText":"You are a Lead Data Engineer. Write a Python Pandas script to clean and transform the following dataset:\n\n### Data Goal:\n{{transformation_goal}}\n\n### Raw Data Sample / Schema:\n```\n{{raw_data_sample}}\n```\n\n### Steps Required:\n1. Handle missing values (imputation or safe dropping).\n2. Normalize date/time columns to UTC ISO format.\n3. Group by key dimensions and compute summary metrics.\n4. Output clean CSV / Parquet export block.","variables":{"transformation_goal":"Clean user transaction logs and aggregate monthly revenue per region","raw_data_sample":"user_id,timestamp,amount,region,status\\n101,2026-08-01 10:00:00,49.99,US,COMPLETED"},"quickTips":["Produces production Python data cleaning scripts."]},{"id":"grok-unfiltered-code-roast","title":"Grok Unfiltered Code Roast & Architecture Audit","description":"Brutally honest, zero-sugarcoating code critique identifying concurrency pitfalls, security flaws, and performance anti-patterns.","category":"debugging","tags":["Grok","Code Audit","Security","Performance Roast","Anti-Patterns"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"grok-4-6","promptText":"$13","variables":{"code_snippet":"async function processBatch(items) { return Promise.all(items.map(async item => { const res = await fetch('/api/' + item.id); return res.json(); })); }","tech_stack":"Node.js 22 / TypeScript / Next.js","critique_severity":"Hardcore roast with deep root-cause explanation and production-grade refactor"},"quickTips":["Grok's unfiltered mode is ideal for cutting through politeness to expose silent memory leaks, concurrency storms, and unhandled errors."]},{"id":"express-security-auditor","title":"OWASP Security Audit & Vulnerability Scanner","description":"Audit code for XSS, SQL Injection, CSRF, ReDoS, insecure direct object references, and auth leaks.","category":"debugging","tags":["Security","OWASP","Vulnerability","Sanitization"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"claude-5-opus","promptText":"You are a Senior Cyber Security Auditor and Penetration Tester. Audit the following {{language}} code for vulnerabilities against OWASP Top 10 standards:\n\n### Code Snippet under Audit:\n```{{language}}\n{{code_snippet}}\n```\n\n### Evaluation Checklist:\n1. Injection risks (SQLi, Command Injection, XSS).\n2. Authentication & Session flaws (Unchecked JWT claims, hardcoded secrets).\n3. Insecure Direct Object References (IDOR).\n4. Memory safety, ReDoS, or Resource Exhaustion.\n\n### Output Format:\n- **Severity Matrix**: List vulnerabilities by High / Medium / Low severity.\n- **Root Cause Explanation**: Why the vulnerability is dangerous.\n- **Hardened Code Patch**: Provide sanitized, hardened security implementation.","variables":{"language":"typescript","code_snippet":"// Paste code to security audit..."},"quickTips":["Identifies OWASP vulnerabilities before code reaches production."]},{"id":"express-bug-fix","title":"Root Cause Bug Diagnostic & Patch","description":"Pinpoint deep runtime bugs, race conditions, memory leaks, or unhandled null references.","category":"debugging","tags":["Debugging","Error Diagnostics","Fix","Root Cause"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"deepseek-v4-pro","promptText":"You are a Principal Systems Auditor and Debugging Specialist.\n\n### Problem Context:\nI am encountering an error in my {{language}} application.\n\n### Error Trace / Symptom:\n```\n{{error_message}}\n```\n\n### Relevant Code Block:\n```{{language}}\n{{code_snippet}}\n```\n\n### Instructions:\n1. Perform step-by-step reasoning to isolate the exact root cause.\n2. Explain WHY the failure occurs under specific execution conditions.\n3. Provide the minimal, surgical patch to fix the bug without causing side effects.","variables":{"language":"typescript","error_message":"TypeError: Cannot read properties of undefined (reading \"map\")","code_snippet":"// Paste failing code block..."},"quickTips":["Include the complete terminal error stack trace.","DeepSeek-V4-Pro will generate a full CoT diagnostic chain."]},{"id":"express-doc-generator","title":"Comprehensive Technical Documentation","description":"Generate beautiful Markdown documentation, TSDoc comments, and usage examples for any module.","category":"documentation","tags":["Documentation","Markdown","TSDoc","API Docs"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"claude-5-sonnet","promptText":"You are a Technical Writer and Developer Relations Lead. Document the following {{language}} module:\n\n### Source Code:\n```{{language}}\n{{code_snippet}}\n```\n\n### Required Structure:\n1. **Overview & Purpose**: High-level summary of what the module does.\n2. **Installation & Import**: Usage syntax snippet.\n3. **API Reference**: Detailed description of parameters, return types, and thrown exceptions.\n4. **Example Code Block**: 2 realistic usage examples (basic and edge case).","variables":{"language":"typescript","code_snippet":"// Paste your class or utility function here..."},"quickTips":["Turn raw codebase utilities into developer-ready README sections."]},{"id":"express-openapi-gen","title":"OpenAPI 3.0 YAML / Swagger Spec Generator","description":"Convert endpoints, DTO models, or controller code into official OpenAPI 3.0 specification YAML.","category":"documentation","tags":["OpenAPI","Swagger","YAML","API Spec"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"gpt-5-6-sol","promptText":"Act as an API Standards Architect. Convert the following API specification into a valid OpenAPI 3.0.3 YAML file:\n\n### API Context:\n{{api_context}}\n\n### Requirements:\n1. Include info block (title, version, description).\n2. Define path routes with HTTP operations, tags, requestBody schemas, and response status codes (200, 400, 401, 500).\n3. Place re-usable DTO schemas under `components/schemas`.","variables":{"api_context":"POST /v1/auth/login and GET /v1/users/me endpoints"},"quickTips":["Generates clean Swagger YAML specs ready for Postman or Swagger UI."]},{"id":"express-saas-landing-copy","title":"High-Converting Developer SaaS Copy","description":"Write persuasive hero section copy, feature grids, taglines, and CTAs for developer products.","category":"marketing","tags":["SaaS","Copywriting","Landing Page","Developer Tools"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"claude-5-sonnet","promptText":"You are an elite Developer Marketing & Copywriting Lead. Write high-converting landing page copy for: {{product_name}}.\n\n### Product Core Value:\n{{product_value_prop}}\n\n### Target Audience:\n{{target_audience}}\n\n### Deliverables:\n1. **Hero Headline & Sub-headline**: Punchy, clear benefit statement.\n2. **Primary & Secondary CTAs**: High-converting button labels.\n3. **3 Core Feature Value Cards**: Title, 2-line description, and icon suggestion.\n4. **Social Proof Hook**: One-liner testimonial placeholder.","variables":{"product_name":"KingPrompt","product_value_prop":"Client-only AI prompt builder that cuts prompt creation time from 5 clicks to 1","target_audience":"Software Engineers, Product Managers, and AI Builders"},"quickTips":["Generates developer-focused SaaS landing page text with zero fluff."]},{"id":"grok-bot-x-viral-thread","title":"Grok Bot X Viral Tech Thread & Post Crafter","description":"Craft high-signal, high-velocity technical threads and posts tailored for Grok and X algorithmic distribution.","category":"marketing","tags":["Grok Bot","X Thread","Social Growth","Viral Hook","Tech Writing"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"grok-4-6","promptText":"$14","variables":{"topic":"Autonomous AI Coding Agents and LLM Architecture in 2026","core_thesis":"Agentic workflows succeed or fail on clean context architectures, not raw model parameter size","target_audience":"Software engineers, tech founders, and AI developers on X","tone_mode":"Sharp, authoritative, high-signal, slightly witty","call_to_action":"Drop your thoughts below and share your stack"},"quickTips":["Grok performs best with punchy, unpadded sentences and strong data hooks.","Keeps formatting optimized for mobile X feeds with whitespace and bold emphasis."]},{"id":"express-product-launch-post","title":"Product Hunt & Hacker News Launch Post","description":"Craft an engaging Show HN / ProductHunt launch post that resonates with technical communities.","category":"marketing","tags":["Product Hunt","Hacker News","Launch","Community"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"claude-5-sonnet","promptText":"Act as a Tech Startup Founder. Draft an authentic, high-engagement launch post for **Hacker News (Show HN)** and **Product Hunt** for:\n\n### Product Description:\n{{product_description}}\n\n### Why We Built It (The Story):\n{{origin_story}}\n\n### Hacker News Rules:\n- Transparent, concise, developer-first tone.\n- Explain the tech stack and open-source / local-first architecture.\n- Ask for feedback from the community.","variables":{"product_description":"An open-source AI directory and dual-mode prompt workbench","origin_story":"We were tired of 5-step prompt forms and wanted a fast 1-click prompt generator with model syntax tuning"},"quickTips":["Tailors tone specifically for technical audiences on HackerNews and Reddit."]},{"id":"express-code-refactor","title":"Modern Code Refactoring & Cleanup","description":"Transform legacy or messy code into clean, typed, idiomatic modern code with error handling.","category":"refactoring","tags":["TypeScript","Refactoring","Clean Code","Best Practices"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"claude-5-sonnet","promptText":"You are an expert Senior Staff Engineer. Refactor the following {{language}} code to adhere to enterprise-grade standards.\n\n### Objectives:\n1. Improve readability, type safety, and modularity.\n2. Remove redundant logic and enforce modern {{framework}} best practices.\n3. Add robust error handling and defensive checks.\n\n### Input Code:\n```{{language}}\n{{code_snippet}}\n```\n\n### Output Requirements:\n- Return the refactored, complete runnable file without placeholders.\n- Include a brief bulleted summary of key improvements made.","variables":{"language":"typescript","framework":"React / Next.js","code_snippet":"// Paste your code here..."},"quickTips":["Paste legacy JS or messy component code.","Works best with Claude 5 Sonnet or DeepSeek-V4-Pro."]},{"id":"express-agent-tool-spec","title":"AI Agent Function Calling & Tool Definition","description":"Generate structured OpenAPI / JSON Schema tool definitions for OpenAI, Anthropic, or CrewAI agents.","category":"system-prompt","tags":["Tool Calling","JSON Schema","Agents","Function Specs"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"gpt-5-6-sol","promptText":"You are an AI Agent Systems Architect. Generate the JSON Schema function/tool definition for an AI agent capability:\n\n### Tool Description:\n{{tool_description}}\n\n### Input Parameters Required:\n{{input_parameters}}\n\n### Requirements:\n1. Generate valid JSON Schema for function parameters (including descriptions, types, and required fields).\n2. Provide the TypeScript handler function signature.\n3. Include explicit error handling for API timeouts or invalid inputs.","variables":{"tool_description":"Execute SQL query against read-only analytics replica and return JSON result","input_parameters":"query string (required), limit number (optional default 100), timeoutMs (optional)"},"quickTips":["Generates exact JSON tool specs for Anthropic Claude or OpenAI Agent function calls."]},{"id":"grok-bot-custom-agent-persona","title":"Grok Bot Custom Agent Persona & Guardrails","description":"Construct a specialized Grok bot system prompt balancing sharp wit, real-time grounding, and rigorous truth-seeking guardrails.","category":"system-prompt","tags":["Grok Bot","System Prompt","Custom Agent","xAI","Guardrails"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"grok-4-6","promptText":"$15","variables":{"bot_name":"Krypton Sentinel","bot_purpose":"Triage GitHub PRs, flag breaking API changes, and challenge architectural trade-offs with witty clarity","humor_and_wit_level":"Dry, intelligent wit with high technical precision (7/10)","truth_seeking_guardrails":"Never hallucinate facts, cite exact line numbers, and verify assumptions against official specifications"},"quickTips":["Grok's persona architecture excels when explicitly defining both the personality tone curve and zero-tolerance accuracy boundaries."]},{"id":"express-system-prompt-builder","title":"Meta System Prompt Architect","description":"Generate a high-performance system prompt tailored for an AI assistant or agent.","category":"system-prompt","tags":["System Prompt","Prompt Engineering","Persona","Guardrails"],"authorName":"KingPrompt","authorUrl":"https://kingprom.pt/","targetModel":"claude-5-sonnet","promptText":"You are a World-Class Prompt Engineer. Construct a high-performance System Prompt for an AI agent with the following role:\n\n### Target Persona / Role:\n{{target_role}}\n\n### Domain & Task Objective:\n{{task_objective}}\n\n### Operating Constraints & Guardrails:\n{{guardrails}}\n\n### Output Format:\nGenerate a structured XML-tagged System Prompt (, , , ) ready to be pasted directly into an LLM configuration or API call.","variables":{"target_role":"Senior DevOps & Kubernetes Infrastructure Specialist","task_objective":"Assist engineers with Helm charts, CI/CD pipeline optimization, and zero-downtime deployments","guardrails":"Never provide destructive terminal commands without explicit confirmation warnings"},"quickTips":["Meta-prompting technique for creating specialized custom GPTs or Anthropic System Prompts."]},{"id":"live-voice-task-agent","title":"Realtime voice agent with background tool use","description":"Voice-first brief with acknowledge-then-act turns for Live dialogue models.","category":"voice-agent","tags":["Gemini Live","Voice Agent","Realtime"],"authorName":"KingPrompt","authorUrl":"$undefined","targetModel":"gemini-3-8-live","promptText":"You are a realtime voice agent. The caller asked: {{user_request}}.\n\n## Tools available\n{{tools_available}}\n\n## Conversation protocol\n1. Acknowledge immediately (one short sentence, e.g. \"Let me check that…\").\n2. Execute tool calls silently in the background while keeping the caller engaged.\n3. Narrate progress briefly between steps, then confirm the outcome and next step.\n\n## Rules\n- Never stay silent longer than one turn while tools run.\n- Confirm destructive actions before executing them.\n- Switch languages mid-conversation if the caller does.","variables":{"user_request":"Check my calendar and book the earliest free slot tomorrow","tools_available":"calendar.read, calendar.book"},"quickTips":["Acknowledge within one sentence before running tools; callers need early feedback.","Narrate multi-step background work so the caller never hears dead air."]}],"skills":[{"id":"check-agent-compatibility","packId":"agent-compatibility","packName":"Agent Compatibility","kind":"workflow","runtime":"cursor-native","title":"check-agent-compatibility","description":"Run the full repository compatibility pass: scanner score, startup path, validation loop, and docs reliability.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$16","rawMarkdown":"$17","relatedFiles":[]},{"id":"cli-for-agents","packId":"cli-for-agent","packName":"CLI for Agents","kind":"workflow","runtime":"portable","title":"cli-for-agents","description":"Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$18","rawMarkdown":"$19","relatedFiles":[]},{"id":"continual-learning","packId":"continual-learning","packName":"Continual Learning","kind":"workflow","runtime":"cursor-native","title":"continual-learning","description":"Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to `agents-memory-updater`.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Continual Learning\n\nKeep `AGENTS.md` current by delegating the memory update flow to one subagent.\n\n## Trigger\n\nUse when the user asks to mine prior chats, maintain `AGENTS.md`, or run the continual-learning loop.\n\n## Workflow\n\n1. Call `agents-memory-updater`.\n2. Return the updater result.\n\n## Guardrails\n\n- Keep the parent skill orchestration-only.\n- Do not mine transcripts or edit files in the parent flow.\n- Do not bypass the subagent.","rawMarkdown":"---\nname: continual-learning\ndescription: Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to `agents-memory-updater`.\ndisable-model-invocation: true\n---\n\n# Continual Learning\n\nKeep `AGENTS.md` current by delegating the memory update flow to one subagent.\n\n## Trigger\n\nUse when the user asks to mine prior chats, maintain `AGENTS.md`, or run the continual-learning loop.\n\n## Workflow\n\n1. Call `agents-memory-updater`.\n2. Return the updater result.\n\n## Guardrails\n\n- Keep the parent skill orchestration-only.\n- Do not mine transcripts or edit files in the parent flow.\n- Do not bypass the subagent.\n","relatedFiles":[]},{"id":"create-plugin-scaffold","packId":"create-plugin","packName":"Create Plugin","kind":"workflow","runtime":"cursor-native","title":"create-plugin-scaffold","description":"Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when starting a new plugin or adding a plugin to a multi-plugin repository.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$1a","rawMarkdown":"$1b","relatedFiles":[]},{"id":"review-plugin-submission","packId":"create-plugin","packName":"Create Plugin","kind":"workflow","runtime":"cursor-native","title":"review-plugin-submission","description":"Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths, and submission quality before publishing.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$1c","rawMarkdown":"$1d","relatedFiles":[]},{"id":"check-compiler-errors","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"check-compiler-errors","description":"Run compile and type-check commands and report failures","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Check compiler errors\n\n## Trigger\n\nCompile or type-check failures are blocking local validation or CI.\n\n## Workflow\n\n1. Run the repo's compile and type-check commands.\n2. Summarize errors by file and type.\n3. Fix the highest-confidence issues first.\n4. Re-run checks until clean or blocked.\n\n## Output\n\n- Current compile and type-check status\n- Error summary grouped by file and category\n- Fixes applied and remaining blockers","rawMarkdown":"---\nname: check-compiler-errors\ndescription: Run compile and type-check commands and report failures\n---\n\n# Check compiler errors\n\n## Trigger\n\nCompile or type-check failures are blocking local validation or CI.\n\n## Workflow\n\n1. Run the repo's compile and type-check commands.\n2. Summarize errors by file and type.\n3. Fix the highest-confidence issues first.\n4. Re-run checks until clean or blocked.\n\n## Output\n\n- Current compile and type-check status\n- Error summary grouped by file and category\n- Fixes applied and remaining blockers\n","relatedFiles":[]},{"id":"control-cli","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"control-cli","description":"Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$1e","rawMarkdown":"$1f","relatedFiles":[]},{"id":"control-ui","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"control-ui","description":"Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$20","rawMarkdown":"$21","relatedFiles":[]},{"id":"deslop","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"deslop","description":"Remove AI-generated code slop and clean up code style","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Remove AI code slop\n\nCheck the diff against main and remove AI-generated slop introduced in the branch.\n\n## Focus Areas\n\n- Extra comments that are unnecessary or inconsistent with local style\n- Defensive checks or try/catch blocks that are abnormal for trusted code paths\n- Casts to `any` used only to bypass type issues\n- Deeply nested code that should be simplified with early returns\n- Other patterns inconsistent with the file and surrounding codebase\n\n## Guardrails\n\n- Keep behavior unchanged unless fixing a clear bug.\n- Prefer minimal, focused edits over broad rewrites.\n- Keep the final summary concise (1-3 sentences).","rawMarkdown":"---\nname: deslop\ndescription: Remove AI-generated code slop and clean up code style\n---\n\n# Remove AI code slop\n\nCheck the diff against main and remove AI-generated slop introduced in the branch.\n\n## Focus Areas\n\n- Extra comments that are unnecessary or inconsistent with local style\n- Defensive checks or try/catch blocks that are abnormal for trusted code paths\n- Casts to `any` used only to bypass type issues\n- Deeply nested code that should be simplified with early returns\n- Other patterns inconsistent with the file and surrounding codebase\n\n## Guardrails\n\n- Keep behavior unchanged unless fixing a clear bug.\n- Prefer minimal, focused edits over broad rewrites.\n- Keep the final summary concise (1-3 sentences).\n","relatedFiles":[]},{"id":"fix-ci","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"fix-ci","description":"Find failing PR checks, inspect logs or external check links, and apply focused fixes","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Fix CI\n\n## Trigger\n\nBranch or PR CI is failing and needs a fast, iterative path to green checks.\n\n## Workflow\n\n1. Resolve the active PR and inspect `gh pr checks --json name,bucket,state,workflow,link`.\n2. Inspect failed jobs and extract the first actionable error. Use GitHub Actions logs when available; otherwise use the check link to identify the failing command or service.\n3. Apply the smallest safe fix.\n4. Push, re-check the PR check set, and repeat until green.\n\n## Guardrails\n\n- Fix one actionable failure at a time.\n- Prefer minimal, low-risk changes before broader refactors.\n- Keep `gh pr checks` as the source of truth for overall PR CI state.\n\n## Output\n\n- Primary failing job and root error\n- Fixes applied in iteration order\n- Current CI status and next action","rawMarkdown":"---\nname: fix-ci\ndescription: Find failing PR checks, inspect logs or external check links, and apply focused fixes\n---\n\n# Fix CI\n\n## Trigger\n\nBranch or PR CI is failing and needs a fast, iterative path to green checks.\n\n## Workflow\n\n1. Resolve the active PR and inspect `gh pr checks --json name,bucket,state,workflow,link`.\n2. Inspect failed jobs and extract the first actionable error. Use GitHub Actions logs when available; otherwise use the check link to identify the failing command or service.\n3. Apply the smallest safe fix.\n4. Push, re-check the PR check set, and repeat until green.\n\n## Guardrails\n\n- Fix one actionable failure at a time.\n- Prefer minimal, low-risk changes before broader refactors.\n- Keep `gh pr checks` as the source of truth for overall PR CI state.\n\n## Output\n\n- Primary failing job and root error\n- Fixes applied in iteration order\n- Current CI status and next action\n","relatedFiles":[]},{"id":"fix-merge-conflicts","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"fix-merge-conflicts","description":"Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Fix merge conflicts\n\n## Trigger\n\nBranch has unresolved merge conflicts and needs a reliable path to a buildable state.\n\n## Workflow\n\n1. Detect all conflicting files from git status and conflict markers.\n2. Resolve each conflict with minimal, correctness-first edits.\n3. Prefer preserving both sides when safe. Otherwise, choose the variant that compiles and keeps public behavior stable.\n4. Regenerate lockfiles with package manager tools instead of hand-editing.\n5. Run compile, lint, and relevant tests.\n6. Stage resolved files and summarize key decisions.\n\n## Guardrails\n\n- Keep changes minimal and readable.\n- Do not leave conflict markers in any file.\n- Avoid broad refactors while resolving conflicts.\n- Do not push or tag during conflict resolution.\n\n## Output\n\n- Files resolved\n- Notable resolution choices\n- Build/test outcome","rawMarkdown":"---\nname: fix-merge-conflicts\ndescription: Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution\n---\n\n# Fix merge conflicts\n\n## Trigger\n\nBranch has unresolved merge conflicts and needs a reliable path to a buildable state.\n\n## Workflow\n\n1. Detect all conflicting files from git status and conflict markers.\n2. Resolve each conflict with minimal, correctness-first edits.\n3. Prefer preserving both sides when safe. Otherwise, choose the variant that compiles and keeps public behavior stable.\n4. Regenerate lockfiles with package manager tools instead of hand-editing.\n5. Run compile, lint, and relevant tests.\n6. Stage resolved files and summarize key decisions.\n\n## Guardrails\n\n- Keep changes minimal and readable.\n- Do not leave conflict markers in any file.\n- Avoid broad refactors while resolving conflicts.\n- Do not push or tag during conflict resolution.\n\n## Output\n\n- Files resolved\n- Notable resolution choices\n- Build/test outcome\n","relatedFiles":[]},{"id":"get-pr-comments","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"get-pr-comments","description":"Fetch and summarize review comments from the active pull request","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Get PR comments\n\n## Trigger\n\nNeed a concise, actionable summary of feedback on the active pull request.\n\n## Workflow\n\n1. Resolve the active PR for the current branch.\n2. Fetch review comments and discussion comments.\n3. Group feedback by severity and actionability.\n4. Return a concise action list.\n\n## Output\n\n- Grouped feedback summary\n- Action list ordered by priority\n- Open questions that still need clarification","rawMarkdown":"---\nname: get-pr-comments\ndescription: Fetch and summarize review comments from the active pull request\n---\n\n# Get PR comments\n\n## Trigger\n\nNeed a concise, actionable summary of feedback on the active pull request.\n\n## Workflow\n\n1. Resolve the active PR for the current branch.\n2. Fetch review comments and discussion comments.\n3. Group feedback by severity and actionability.\n4. Return a concise action list.\n\n## Output\n\n- Grouped feedback summary\n- Action list ordered by priority\n- Open questions that still need clarification","relatedFiles":[]},{"id":"loop-on-ci","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"loop-on-ci","description":"Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$22","rawMarkdown":"$23","relatedFiles":[]},{"id":"make-pr-easy-to-review","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"make-pr-easy-to-review","description":"Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for \"make this easy to review\", \"tidy this PR\", \"clean up commits\", or \"annotate the diff\".","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$24","rawMarkdown":"$25","relatedFiles":[]},{"id":"new-branch-and-pr","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"new-branch-and-pr","description":"Create a fresh branch, complete work, and open a pull request","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# New branch and PR\n\n## Trigger\n\nStarting work that should be shipped through a clean branch and pull request workflow.\n\n## Workflow\n\n1. Ensure the working tree is clean or explicitly handled.\n2. Create a descriptive branch from the latest main.\n3. Complete implementation and tests.\n4. Commit focused changes and push.\n5. Create a concise PR with summary and test notes.\n\n## Guardrails\n\n- Keep branch scope focused on one change set.\n- Include verification notes before requesting review.\n\n## Output\n\n- New branch name\n- PR summary and test notes\n- PR URL","rawMarkdown":"---\nname: new-branch-and-pr\ndescription: Create a fresh branch, complete work, and open a pull request\n---\n\n# New branch and PR\n\n## Trigger\n\nStarting work that should be shipped through a clean branch and pull request workflow.\n\n## Workflow\n\n1. Ensure the working tree is clean or explicitly handled.\n2. Create a descriptive branch from the latest main.\n3. Complete implementation and tests.\n4. Commit focused changes and push.\n5. Create a concise PR with summary and test notes.\n\n## Guardrails\n\n- Keep branch scope focused on one change set.\n- Include verification notes before requesting review.\n\n## Output\n\n- New branch name\n- PR summary and test notes\n- PR URL\n","relatedFiles":[]},{"id":"pr-review-canvas","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"pr-review-canvas","description":"Generate an interactive PR review walkthrough as an HTML page. Fetches PR data via gh API, categorizes files into core vs mechanical changes, adds reviewer annotations, and renders diffs with moved-code detection. Use when the user pastes a GitHub PR URL and asks for a review, walkthrough, or summary, or says \"review this PR\".","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$26","rawMarkdown":"$27","relatedFiles":[]},{"id":"review-and-ship","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"review-and-ship","description":"Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$28","rawMarkdown":"$29","relatedFiles":[]},{"id":"run-smoke-tests","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"run-smoke-tests","description":"Run Playwright smoke tests, debug failures, and verify fixes","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Run smoke tests\n\n## Trigger\n\nNeed end-to-end smoke verification before or after changes.\n\n## Workflow\n\n1. Build prerequisites for the target app.\n2. Run the relevant smoke suite or a focused test file.\n3. If failing, inspect traces/logs and isolate the root cause.\n4. Apply a minimal fix and rerun until stable.\n\n## Example Commands\n\n```bash\n# Run full smoke suite\nnpm run smoketest\n\n# Run a specific smoke test file\nnpm run smoketest -- path/to/test.spec.ts\n\n# Faster iteration when build artifacts are ready\nnpm run smoketest-no-compile -- path/to/test.spec.ts\n```\n\n## Guardrails\n\n- Prefer deterministic waits and assertions over brittle timeouts.\n- Re-run passing fixes to reduce flaky false positives.\n- Quarantine tests only when explicitly requested and documented.\n\n## Output\n\n- Test results summary\n- Root cause and fix\n- Remaining flake risk (if any)","rawMarkdown":"---\nname: run-smoke-tests\ndescription: Run Playwright smoke tests, debug failures, and verify fixes\n---\n\n# Run smoke tests\n\n## Trigger\n\nNeed end-to-end smoke verification before or after changes.\n\n## Workflow\n\n1. Build prerequisites for the target app.\n2. Run the relevant smoke suite or a focused test file.\n3. If failing, inspect traces/logs and isolate the root cause.\n4. Apply a minimal fix and rerun until stable.\n\n## Example Commands\n\n```bash\n# Run full smoke suite\nnpm run smoketest\n\n# Run a specific smoke test file\nnpm run smoketest -- path/to/test.spec.ts\n\n# Faster iteration when build artifacts are ready\nnpm run smoketest-no-compile -- path/to/test.spec.ts\n```\n\n## Guardrails\n\n- Prefer deterministic waits and assertions over brittle timeouts.\n- Re-run passing fixes to reduce flaky false positives.\n- Quarantine tests only when explicitly requested and documented.\n\n## Output\n\n- Test results summary\n- Root cause and fix\n- Remaining flake risk (if any)\n","relatedFiles":[]},{"id":"thermo-nuclear-code-quality-review","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"thermo-nuclear-code-quality-review","description":"Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$2a","rawMarkdown":"$2b","relatedFiles":[]},{"id":"verify-this","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"verify-this","description":"Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$2c","rawMarkdown":"$2d","relatedFiles":[]},{"id":"weekly-review","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"weekly-review","description":"Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Weekly review\n\n## Trigger\n\nNeed a weekly recap of shipped work for status updates, retros, or planning.\n\n## Workflow\n\n1. Determine the current git user email from repo config.\n2. Collect authored commits from the last 7-10 days on the primary branch context.\n3. Exclude merge commits.\n4. Group meaningful changes into 2-5 concise bullets.\n5. Add a short classification paragraph covering:\n - likely bug fixes\n - likely tech debt work\n - likely net-new functionality\n\n## Guardrails\n\n- Keep the recap short and executive-readable.\n- Base claims only on commit history and diffs.\n- If git email is missing, ask the user to set it before proceeding.\n\n## Output\n\n- 2-5 bullet weekly summary\n- Brief classification paragraph (bugfix / tech debt / net-new)","rawMarkdown":"---\nname: weekly-review\ndescription: Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work\n---\n\n# Weekly review\n\n## Trigger\n\nNeed a weekly recap of shipped work for status updates, retros, or planning.\n\n## Workflow\n\n1. Determine the current git user email from repo config.\n2. Collect authored commits from the last 7-10 days on the primary branch context.\n3. Exclude merge commits.\n4. Group meaningful changes into 2-5 concise bullets.\n5. Add a short classification paragraph covering:\n - likely bug fixes\n - likely tech debt work\n - likely net-new functionality\n\n## Guardrails\n\n- Keep the recap short and executive-readable.\n- Base claims only on commit history and diffs.\n- If git email is missing, ask the user to set it before proceeding.\n\n## Output\n\n- 2-5 bullet weekly summary\n- Brief classification paragraph (bugfix / tech debt / net-new)\n","relatedFiles":[]},{"id":"what-did-i-get-done","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"what-did-i-get-done","description":"Summarize authored commits over a user-specified time period into a concise update","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# What did I get done\n\n## Trigger\n\nNeed a short, high-signal summary of work completed in a specific time range (for example: yesterday, last 3 days, or last week).\n\n## Workflow\n\n1. Resolve the requested time window into concrete dates.\n2. Read commits authored by the current git user email within that range.\n3. Exclude merge commits and uncommitted changes.\n4. Synthesize the most important shipped changes into a concise status update.\n5. Include the actual date range used in the final summary.\n\n## Guardrails\n\n- Be extremely concise and information-dense.\n- Prioritize substantial behavior or architecture changes.\n- Omit cosmetic-only changes (formatting, imports, minor renames).\n- Do not infer intent or motivation. Describe changes functionally.\n\n## Output\n\n- One short summary suitable for a status update\n- Real date range\n- Optional 2-5 bullets for major changes only","rawMarkdown":"---\nname: what-did-i-get-done\ndescription: Summarize authored commits over a user-specified time period into a concise update\n---\n\n# What did I get done\n\n## Trigger\n\nNeed a short, high-signal summary of work completed in a specific time range (for example: yesterday, last 3 days, or last week).\n\n## Workflow\n\n1. Resolve the requested time window into concrete dates.\n2. Read commits authored by the current git user email within that range.\n3. Exclude merge commits and uncommitted changes.\n4. Synthesize the most important shipped changes into a concise status update.\n5. Include the actual date range used in the final summary.\n\n## Guardrails\n\n- Be extremely concise and information-dense.\n- Prioritize substantial behavior or architecture changes.\n- Omit cosmetic-only changes (formatting, imports, minor renames).\n- Do not infer intent or motivation. Describe changes functionally.\n\n## Output\n\n- One short summary suitable for a status update\n- Real date range\n- Optional 2-5 bullets for major changes only\n","relatedFiles":[]},{"id":"workflow-from-chats","packId":"cursor-team-kit","packName":"Cursor Team Kit","kind":"workflow","runtime":"cursor-native","title":"workflow-from-chats","description":"Extract durable working preferences from recent Cursor chats and convert them into skills, rules, or workflow docs. Use when asked to learn preferences, mine feedback, personalize workflows, or generate team/person-specific agent guidance.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$2e","rawMarkdown":"$2f","relatedFiles":[]},{"id":"orchestrate","packId":"orchestrate","packName":"Orchestrate","kind":"workflow","runtime":"cursor-native","title":"orchestrate","description":"Use only when the user explicitly types `/orchestrate ` to decompose a large task, spawn a tree of parallel cloud-agent workers/subplanners/verifiers via the Cursor SDK, and collect structured handoffs; do not invoke autonomously.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$30","rawMarkdown":"$31","relatedFiles":[{"path":"prompts/andon-block.md","title":"Andon Block","content":"\n### Andon\nHalts new spawns across the whole tree. Raise only with concrete evidence that continued spawning produces garbage: upstream output is wrong and downstream tasks will fail against it, verifier cascade shows acceptance was wrong, auth or infra is unrecoverable. A task hitting its own snag is a `Status: blocked` handoff, not Andon.\n\n bun /scripts/cli.ts andon raise --reason \"\"{{agentIdFlag}} --workspace \n\n`--reason` is required and posts to the run thread so the tree can see why orchestration paused. The reaction is the cheap gate children poll. `--agent-id` adds a footer link back to the agent that raised it.\n"},{"path":"prompts/empty-error-handoff.md","title":"Empty Error Handoff","content":"Cloud run errored before producing a final message.\n\nagent: https://cursor.com/agents/{{agentId}}\nagentId: {{agentId}}\nrunId: {{runId}}\nresultStatus: {{resultStatus}}\nresult:\n```json\n{{resultDataJson}}\n```\n"},{"path":"prompts/failure-handoff.md","title":"Failure Handoff","content":"\n\n# {{taskName}} failure handoff\n\nStatus: error (cloud agent terminated without writing a handoff)\nFailure mode: {{failureMode}}\nCloud agent: {{agentId}}\nStarted: {{startedAt}}\nTerminated: {{terminatedAt}}\nDuration: {{duration}}\nLast activity: {{lastActivityLine}}\nLast tool call: {{lastToolCall}}\nBranch: {{branch}}\nSDK error: {{sdkError}}\n\n## Suggested next steps\n{{suggestions}}\n"},{"path":"prompts/finished-no-handoff.md","title":"Finished No Handoff","content":"\n\n# {{taskName}} finished without handoff\n\nStatus: {{resultStatus}} (cloud agent ended cleanly but never wrote a `## Status` handoff)\nCloud agent: {{agentId}}\nRun: {{runId}}\nBranch: {{branch}}\nTerminated: {{terminatedAt}}\n\n## Suggested next steps\n- Inspect the raw handoff at `handoffs/{{taskName}}.md` to see what the worker actually emitted.\n- Retry as-is if this looks like a prompt-misfire (worker produced prose but not the structured template).\n- Abandon: skip task, replan around it if the goal genuinely has no acceptable output.{{rawSnippetBlock}}\n"},{"path":"prompts/loop-hygiene.md","title":"Loop Hygiene","content":"$32"},{"path":"prompts/root.md","title":"Root","content":"You are the root planner for: {{goal}}\n\nRead this skill's `SKILL.md` and follow it.\n\nYour cloud agent id is `{{agentId}}`. Set `plan.selfAgentId` in plan.json to that string so spawns record `parentAgentId` and `kill-tree --agent-id` can target this planner.\n\nWrite `plan.summary` as a one-line orientation for the human in the Slack thread (e.g. `\"smoke test of the new orchestrate substrate\"`). Kickoff posts the summary; without it, kickoff falls back to a truncated `goal`.{{dispatcherInstruction}}{{slackChannelInstruction}}\n\nDiscover here before you publish tasks. Bootstrap workers hold reference material for descendants, not one-off discovery.\n\n{{loopHygiene}}\n"},{"path":"prompts/slack-block.md","title":"Slack Block","content":"$33"},{"path":"prompts/subplanner.md","title":"Subplanner","content":"$34"},{"path":"prompts/verifier.md","title":"Verifier","content":"$35"},{"path":"prompts/worker.md","title":"Worker","content":"$36"},{"path":"references/dispatcher.md","title":"Dispatcher","content":"$37"},{"path":"references/handoffs.md","title":"Handoffs","content":"$38"},{"path":"references/planner.md","title":"Planner","content":"$39"},{"path":"references/spawning.md","title":"Spawning","content":"$3a"},{"path":"scripts/adapters/README.md","title":"README","content":"$3b"}]},{"id":"architect","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"architect","description":"Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$3c","rawMarkdown":"$3d","relatedFiles":[{"path":"references/design-red-flags.md","title":"Design Red Flags","content":"$3e"},{"path":"references/rationale-template.md","title":"Rationale Template","content":"$3f"},{"path":"references/runner-prompt.md","title":"Runner Prompt","content":"$40"}]},{"id":"arena","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"cursor-native","title":"arena","description":"Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$41","rawMarkdown":"$42","relatedFiles":[]},{"id":"automate-me","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"cursor-native","title":"automate-me","description":"Use for \"automate me\", \"create/update/refresh my -mode skill\", \"turn/capture my preferences or working style into a skill\", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$43","rawMarkdown":"$44","relatedFiles":[]},{"id":"blast-radius","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"blast-radius","description":"Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$45","rawMarkdown":"$46","relatedFiles":[]},{"id":"bro","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"bro","description":"Restate the last message in plain human language, with no jargon.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"Restate your last message. Stop using jargon and speak coherently. State it more simply and concisely, like one human talking to another.","rawMarkdown":"---\nname: bro\ndescription: Restate the last message in plain human language, with no jargon.\ndisable-model-invocation: true\n---\n\nRestate your last message. Stop using jargon and speak coherently. State it more simply and concisely, like one human talking to another.\n","relatedFiles":[]},{"id":"create-verification-skill","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"create-verification-skill","description":"Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$47","rawMarkdown":"$48","relatedFiles":[{"path":"references/feature-map-example/README.md","title":"README","content":"$49"},{"path":"references/feature-map-example/create-note.md","title":"Create Note","content":"$4a"},{"path":"references/feature-map-example/search.md","title":"Search","content":"$4b"}]},{"id":"figure-it-out","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"figure-it-out","description":"Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$4c","rawMarkdown":"$4d","relatedFiles":[]},{"id":"how","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"how","description":"Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$4e","rawMarkdown":"$4f","relatedFiles":[{"path":"references/critic-prompt.md","title":"Critic Prompt","content":"$50"},{"path":"references/critique-rubric.md","title":"Critique Rubric","content":"$51"},{"path":"references/explainer-prompt.md","title":"Explainer Prompt","content":"$52"},{"path":"references/explorer-prompt.md","title":"Explorer Prompt","content":"$53"}]},{"id":"interrogate","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"cursor-native","title":"interrogate","description":"Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$54","rawMarkdown":"$55","relatedFiles":[{"path":"references/code-quality-review.md","title":"Code Quality Review","content":"$56"},{"path":"references/lead-judgment.md","title":"Lead Judgment","content":"$57"},{"path":"references/reviewer-prompt.md","title":"Reviewer Prompt","content":"$58"},{"path":"references/rubric.md","title":"Rubric","content":"$59"}]},{"id":"maintain-verification-skill","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"maintain-verification-skill","description":"Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or \"audit the verify skill\".","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$5a","rawMarkdown":"$5b","relatedFiles":[]},{"id":"make-bot-ui","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"cursor-native","title":"Make Bot UI","description":"Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$5c","rawMarkdown":"$5d","relatedFiles":[]},{"id":"no-comments","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"no-comments","description":"Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$5e","rawMarkdown":"$5f","relatedFiles":[]},{"id":"poteto-mode","packId":"pstack","packName":"pstack","kind":"mode","runtime":"cursor-native","title":"Poteto Mode","description":"poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$60","rawMarkdown":"$61","relatedFiles":[{"path":"playbooks/authoring-a-skill.md","title":"Authoring A Skill","content":"### Authoring or modifying a skill\n\n**You own the skill's voice.** Agent-facing prose has a higher bar than human prose; unhelpful sentences become instructions.\n\n1. Use the **create-skill** skill (Cursor's built-in for authoring SKILL.md files).\n2. Validate the skill: frontmatter has `name` and `description`, referenced files exist, cross-skill links resolve.\n3. Test cases if structural; skip if subjective.\n4. Run **Opening a PR**.\n\nWhen in doubt, delete; prose earns its keep by changing a decision. Tell it to do the thing and skip the reason. Explain only when the rule is confusing without one. Match tone to scope. Point at structural sources (types, READMEs, config); hardcoded details go stale (the **encode-lessons-in-structure** principle skill). Delegate to other skills by path; don't restate. A workflow you keep hitting but isn't captured → propose a new skill.\n\n**Reply:** summary of the skill, key design decisions, validation notes.\n"},{"path":"playbooks/autonomous-run.md","title":"Autonomous Run","content":"$62"},{"path":"playbooks/autopilot-full.md","title":"Autopilot Full","content":"$63"},{"path":"playbooks/autopilot-stack.md","title":"Autopilot Stack","content":"$64"},{"path":"playbooks/babysit.md","title":"Babysit","content":"$65"},{"path":"playbooks/bug-fix.md","title":"Bug Fix","content":"$66"},{"path":"playbooks/eval.md","title":"Eval","content":"$67"},{"path":"playbooks/feature.md","title":"Feature","content":"$68"},{"path":"playbooks/hillclimb.md","title":"Hillclimb","content":"$69"},{"path":"playbooks/investigation.md","title":"Investigation","content":"$6a"},{"path":"playbooks/multi-phase-plan.md","title":"Multi Phase Plan","content":"$6b"},{"path":"playbooks/opening-a-pr.md","title":"Opening A Pr","content":"$6c"},{"path":"playbooks/orchestrate.md","title":"Orchestrate","content":"$6d"},{"path":"playbooks/pause-safely.md","title":"Pause Safely","content":"$6e"},{"path":"playbooks/perf-issue.md","title":"Perf Issue","content":"$6f"},{"path":"playbooks/prototype.md","title":"Prototype","content":"$70"},{"path":"playbooks/refactoring.md","title":"Refactoring","content":"$71"},{"path":"playbooks/runtime-forensics.md","title":"Runtime Forensics","content":"$72"},{"path":"playbooks/session-pickup.md","title":"Session Pickup","content":"$73"},{"path":"playbooks/shipping.md","title":"Shipping","content":"$74"},{"path":"playbooks/trace-forensics.md","title":"Trace Forensics","content":"$75"},{"path":"playbooks/visual-parity.md","title":"Visual Parity","content":"$76"},{"path":"playbooks/worktree-cleanup.md","title":"Worktree Cleanup","content":"$77"},{"path":"references/bugbot-triage.md","title":"Bugbot Triage","content":"$78"}]},{"id":"principle-boundary-discipline","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-boundary-discipline","description":"Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$79","rawMarkdown":"$7a","relatedFiles":[]},{"id":"principle-build-the-lever","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-build-the-lever","description":"Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$7b","rawMarkdown":"$7c","relatedFiles":[]},{"id":"principle-encode-lessons-in-structure","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-encode-lessons-in-structure","description":"Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$7d","rawMarkdown":"$7e","relatedFiles":[]},{"id":"principle-exhaust-the-design-space","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-exhaust-the-design-space","description":"Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"# Exhaust the Design Space\n\nWhen a novel interaction or architectural decision has no established precedent, explore several concrete alternatives before implementation. Building the wrong thing costs more than exploring three options.\n\n**The rule.** When the right answer is not obvious, build 2-3 competing prototypes or sketches. Compare them side by side. Only then commit. Design it twice is this rule by another name. A second flavor of the first shape does not count.\n\n**When it applies:**\n- Novel UI interactions (no prior art in the codebase)\n- Architectural choices with multiple viable approaches\n- Product design decisions where user experience depends on feel, not logic\n\n**When it doesn't:**\n- Mechanical implementation where the pattern is established\n- Bug fixes or refactors with a clear target state\n- Changes where constraints dictate a single viable approach","rawMarkdown":"$7f","relatedFiles":[]},{"id":"principle-experience-first","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-experience-first","description":"Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$80","rawMarkdown":"$81","relatedFiles":[]},{"id":"principle-fix-root-causes","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-fix-root-causes","description":"Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$82","rawMarkdown":"$83","relatedFiles":[]},{"id":"principle-foundational-thinking","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-foundational-thinking","description":"Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$84","rawMarkdown":"$85","relatedFiles":[]},{"id":"principle-guard-the-context-window","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-guard-the-context-window","description":"Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"# Guard the Context Window\n\nThe context window is finite and non-renewable within a session. Every token that enters should earn its place.\n\n**Why:** Context overflow degrades reasoning quality, creates compression artifacts, and halts progress. Unlike compute or time, context spent inside a session cannot be reclaimed.\n\n**Pattern:**\n- **Isolate large payloads.** Route verbose outputs, screenshots, and large documents to subagents. The main context gets summaries, not raw data.\n- **Don't read what you won't use.** Read selectively based on relevance. If a file isn't needed for the current task, skip it.\n- **Keep frequently used content inline.** Templates and references used on every invocation belong in the skill file, not in separate files that cost a read each time.\n- **Size phases and cap scope.** Limit files per phase, set turn budgets, account for mechanism costs.","rawMarkdown":"$86","relatedFiles":[]},{"id":"principle-laziness-protocol","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-laziness-protocol","description":"Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$87","rawMarkdown":"$88","relatedFiles":[]},{"id":"principle-make-operations-idempotent","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-make-operations-idempotent","description":"Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$89","rawMarkdown":"$8a","relatedFiles":[]},{"id":"principle-migrate-callers-then-delete-legacy-apis","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-migrate-callers-then-delete-legacy-apis","description":"Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"# Migrate Callers Then Delete Legacy APIs\n\nWhen we decide a new API is the right design, migrate callers and remove the old API in the same refactor wave instead of preserving compatibility layers.\n\n**Rule:**\n- Do not keep legacy API paths alive only because internal callers still exist\n- Inventory callers, migrate them, and delete the old API immediately\n- Treat temporary adapters as exceptional and time-boxed, not default architecture\n- Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details\n\n**When this applies:**\n- No external users depend on backward compatibility\n- The project can absorb coordinated breaking changes\n- The new API is part of a simplification or refactor initiative\n\nKeeping both old and new APIs creates dual-path complexity, slows cleanup, and makes the codebase feel append-only.","rawMarkdown":"$8b","relatedFiles":[]},{"id":"principle-minimize-reader-load","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-minimize-reader-load","description":"Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$8c","rawMarkdown":"$8d","relatedFiles":[]},{"id":"principle-model-the-domain","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-model-the-domain","description":"Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$8e","rawMarkdown":"$8f","relatedFiles":[]},{"id":"principle-never-block-on-the-human","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-never-block-on-the-human","description":"Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$90","rawMarkdown":"$91","relatedFiles":[]},{"id":"principle-outcome-oriented-execution","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-outcome-oriented-execution","description":"Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"# Outcome-Oriented Execution\n\nOptimize for the intended, verifiable end state rather than preserving smooth intermediate states.\n\n**Why:** Keeping every intermediate step fully stable often creates temporary compatibility code that becomes long-lived debt. Converge on the target architecture and prove correctness at explicit verification boundaries.\n\n**Core rule:**\n- Prioritize end-state integrity over transitional stability\n- Intermediate breakage is acceptable when it is planned, scoped, and reversible\n- Always run final verification before declaring done\n\n**Guardrails:**\n- Use this for planned rewrites and migrations with explicit phase boundaries\n- Declare where temporary breakage is acceptable\n- Keep high-signal checks for actively touched areas while migrating\n- Require full static and runtime verification at plan completion","rawMarkdown":"$92","relatedFiles":[]},{"id":"principle-prove-it-works","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-prove-it-works","description":"Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$93","rawMarkdown":"$94","relatedFiles":[]},{"id":"principle-redesign-from-first-principles","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-redesign-from-first-principles","description":"Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"# Redesign From First Principles\n\nWhen integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been there from the start. The result should look like what we would have built if we'd known on day one.\n\n- Read all affected files and understand the current design holistically\n- Ask: \"if we were writing this from scratch with this new requirement, what would we build?\"\n- Propagate the change through every reference: types, docs, examples, rationale sections\n- Think about the redesign holistically, then deliver it incrementally\n\nThis is the method for preserving option value when integrating changes into an existing design.","rawMarkdown":"---\nname: principle-redesign-from-first-principles\ndescription: \"Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.\"\ndisable-model-invocation: true\n---\n\n# Redesign From First Principles\n\nWhen integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been there from the start. The result should look like what we would have built if we'd known on day one.\n\n- Read all affected files and understand the current design holistically\n- Ask: \"if we were writing this from scratch with this new requirement, what would we build?\"\n- Propagate the change through every reference: types, docs, examples, rationale sections\n- Think about the redesign holistically, then deliver it incrementally\n\nThis is the method for preserving option value when integrating changes into an existing design.\n","relatedFiles":[]},{"id":"principle-separate-before-serializing-shared-state","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-separate-before-serializing-shared-state","description":"Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$95","rawMarkdown":"$96","relatedFiles":[]},{"id":"principle-sequence-verifiable-units","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-sequence-verifiable-units","description":"Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$97","rawMarkdown":"$98","relatedFiles":[]},{"id":"principle-subtract-before-you-add","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-subtract-before-you-add","description":"Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$99","rawMarkdown":"$9a","relatedFiles":[]},{"id":"principle-type-system-discipline","packId":"pstack","packName":"pstack","kind":"principle","runtime":"portable","title":"principle-type-system-discipline","description":"Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$9b","rawMarkdown":"$9c","relatedFiles":[]},{"id":"recall","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"cursor-native","title":"recall","description":"Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$9d","rawMarkdown":"$9e","relatedFiles":[]},{"id":"reflect","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"cursor-native","title":"reflect","description":"Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$9f","rawMarkdown":"$a0","relatedFiles":[{"path":"references/divergent-reviewer.md","title":"Divergent Reviewer","content":"$a1"},{"path":"references/judgment-reviewer.md","title":"Judgment Reviewer","content":"$a2"},{"path":"references/synthesizer.md","title":"Synthesizer","content":"$a3"},{"path":"references/tooling-reviewer.md","title":"Tooling Reviewer","content":"$a4"}]},{"id":"setup-pstack","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"cursor-native","title":"setup-pstack","description":"Configure which models pstack uses per role. Detects your available models and writes an always-applied rule that overrides the skill defaults. Use for /setup-pstack, \"configure pstack models\", or changing pstack's model choices.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$a5","rawMarkdown":"$a6","relatedFiles":[]},{"id":"show-me-your-work","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"show-me-your-work","description":"Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$a7","rawMarkdown":"$a8","relatedFiles":[]},{"id":"swarm","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"cursor-native","title":"swarm","description":"Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$a9","rawMarkdown":"$aa","relatedFiles":[]},{"id":"tdd","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"tdd","description":"Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$ab","rawMarkdown":"$ac","relatedFiles":[]},{"id":"teach","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"teach","description":"Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$ad","rawMarkdown":"$ae","relatedFiles":[]},{"id":"technical-writing","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"technical-writing","description":"Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$af","rawMarkdown":"$b0","relatedFiles":[]},{"id":"typescript-best-practices","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"typescript-best-practices","description":"TypeScript best practices. Use when reading or editing any .ts or .tsx file.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$b1","rawMarkdown":"$b2","relatedFiles":[{"path":"references/patterns.md","title":"Patterns","content":"$b3"}]},{"id":"unslop","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"unslop","description":"Cut AI tells from any writing. Must always apply.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$b4","rawMarkdown":"$b5","relatedFiles":[]},{"id":"why","packId":"pstack","packName":"pstack","kind":"workflow","runtime":"portable","title":"why","description":"Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","authorName":"Lauren Tan","authorUrl":"https://github.com/poteto","body":"$b6","rawMarkdown":"$b7","relatedFiles":[{"path":"references/epistemics.md","title":"Epistemics","content":"$b8"},{"path":"references/investigator-prompt.md","title":"Investigator Prompt","content":"$b9"},{"path":"references/source-playbook.md","title":"Source Playbook","content":"$ba"},{"path":"references/sources/code-archaeology.md","title":"Code Archaeology","content":"$bb"},{"path":"references/sources/databricks.md","title":"Databricks","content":"$bc"},{"path":"references/sources/datadog.md","title":"Datadog","content":"$bd"},{"path":"references/sources/incident-postmortem.md","title":"Incident Postmortem","content":"$be"},{"path":"references/sources/linear.md","title":"Linear","content":"$bf"},{"path":"references/sources/notion.md","title":"Notion","content":"$c0"},{"path":"references/sources/sentry.md","title":"Sentry","content":"$c1"},{"path":"references/sources/slack.md","title":"Slack","content":"$c2"},{"path":"references/synthesizer-prompt.md","title":"Synthesizer Prompt","content":"$c3"}]},{"id":"cancel-ralph","packId":"ralph-loop","packName":"Ralph Loop","kind":"workflow","runtime":"cursor-native","title":"cancel-ralph","description":"Cancel an active Ralph Loop. Use when the user wants to stop, cancel, or abort a running ralph loop.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Cancel Ralph\n\n## Trigger\n\nThe user wants to cancel or stop an active Ralph loop.\n\n## Workflow\n\n1. Check if `.cursor/ralph/scratchpad.md` exists.\n\n2. **If it does not exist**: Tell the user \"No active Ralph loop found.\"\n\n3. **If it exists**:\n - Read `.cursor/ralph/scratchpad.md` to get the current iteration from the `iteration:` field.\n - Remove the state file and any done flag:\n ```bash\n rm -rf .cursor/ralph\n ```\n - Report: \"Cancelled Ralph loop (was at iteration N).\"\n\n## Output\n\nA short confirmation with the iteration count, or a message that no loop was active.","rawMarkdown":"---\nname: cancel-ralph\ndescription: Cancel an active Ralph Loop. Use when the user wants to stop, cancel, or abort a running ralph loop.\n---\n\n# Cancel Ralph\n\n## Trigger\n\nThe user wants to cancel or stop an active Ralph loop.\n\n## Workflow\n\n1. Check if `.cursor/ralph/scratchpad.md` exists.\n\n2. **If it does not exist**: Tell the user \"No active Ralph loop found.\"\n\n3. **If it exists**:\n - Read `.cursor/ralph/scratchpad.md` to get the current iteration from the `iteration:` field.\n - Remove the state file and any done flag:\n ```bash\n rm -rf .cursor/ralph\n ```\n - Report: \"Cancelled Ralph loop (was at iteration N).\"\n\n## Output\n\nA short confirmation with the iteration count, or a message that no loop was active.\n","relatedFiles":[]},{"id":"ralph-loop","packId":"ralph-loop","packName":"Ralph Loop","kind":"workflow","runtime":"cursor-native","title":"ralph-loop","description":"Start a Ralph Loop for iterative self-referential development. Use when the user asks to run a ralph loop, start an iterative loop, or wants repeated autonomous iteration on a task until completion.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$c4","rawMarkdown":"$c5","relatedFiles":[]},{"id":"ralph-loop-help","packId":"ralph-loop","packName":"Ralph Loop","kind":"workflow","runtime":"cursor-native","title":"ralph-loop-help","description":"Explain the Ralph Loop plugin, how it works, and available skills. Use when the user asks for help with ralph loop, wants to understand the technique, or needs usage examples.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$c6","rawMarkdown":"$c7","relatedFiles":[]},{"id":"create-learning-path","packId":"teaching","packName":"Teaching","kind":"workflow","runtime":"portable","title":"create-learning-path","description":"Build a personalized learning roadmap with milestones and practice checkpoints","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Create a learning path\n\n## Trigger\n\nBuilding capability in a topic over multiple sessions.\n\n## Workflow\n\n1. Assess baseline knowledge and target outcomes.\n2. Sequence topics from fundamentals to applied practice.\n3. Define milestone projects and time-boxed checkpoints.\n4. Add deliberate practice exercises with feedback criteria.\n5. Review progress and adjust pacing.\n\n## Tools\n\n- Use Ask user tool.\n\n## Guardrails\n\n- Keep milestones achievable within the stated schedule.\n- Include practice and reflection in every phase.\n- Avoid resource overload by prioritizing a small set of materials.\n\n## Output\n\n- Week-by-week or milestone-based plan\n- Practice assignments\n- Progress review rubric","rawMarkdown":"---\nname: create-learning-path\ndescription: Build a personalized learning roadmap with milestones and practice checkpoints\n---\n\n# Create a learning path\n\n## Trigger\n\nBuilding capability in a topic over multiple sessions.\n\n## Workflow\n\n1. Assess baseline knowledge and target outcomes.\n2. Sequence topics from fundamentals to applied practice.\n3. Define milestone projects and time-boxed checkpoints.\n4. Add deliberate practice exercises with feedback criteria.\n5. Review progress and adjust pacing.\n\n## Tools\n\n- Use Ask user tool.\n\n## Guardrails\n\n- Keep milestones achievable within the stated schedule.\n- Include practice and reflection in every phase.\n- Avoid resource overload by prioritizing a small set of materials.\n\n## Output\n\n- Week-by-week or milestone-based plan\n- Practice assignments\n- Progress review rubric\n","relatedFiles":[]},{"id":"run-learning-retrospective","packId":"teaching","packName":"Teaching","kind":"workflow","runtime":"portable","title":"run-learning-retrospective","description":"Evaluate learning progress, identify blockers, and adjust the learning plan","authorName":"Cursor","authorUrl":"https://cursor.com","body":"# Run a learning retrospective\n\n## Trigger\n\nLearner completed a milestone and needs data-driven adjustment to their plan.\n\n## Workflow\n\n1. Review completed work against target outcomes.\n2. Identify recurring blockers and weak concepts.\n3. Prioritize what to reinforce versus what to defer.\n4. Adjust pacing and upcoming practice tasks.\n5. Set next milestone and measurable checkpoint.\n\n## Tools\n\n- Use Ask user tool.\n\n## Output\n\n- Progress retrospective\n- Updated learning plan\n- Next milestone definition","rawMarkdown":"---\nname: run-learning-retrospective\ndescription: Evaluate learning progress, identify blockers, and adjust the learning plan\n---\n\n# Run a learning retrospective\n\n## Trigger\n\nLearner completed a milestone and needs data-driven adjustment to their plan.\n\n## Workflow\n\n1. Review completed work against target outcomes.\n2. Identify recurring blockers and weak concepts.\n3. Prioritize what to reinforce versus what to defer.\n4. Adjust pacing and upcoming practice tasks.\n5. Set next milestone and measurable checkpoint.\n\n## Tools\n\n- Use Ask user tool.\n\n## Output\n\n- Progress retrospective\n- Updated learning plan\n- Next milestone definition\n","relatedFiles":[]},{"id":"thermo-nuclear-code-quality-review","packId":"thermos","packName":"Thermos","kind":"workflow","runtime":"cursor-native","title":"thermo-nuclear-code-quality-review","description":"Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$c8","rawMarkdown":"$c9","relatedFiles":[]},{"id":"thermo-nuclear-review","packId":"thermos","packName":"Thermos","kind":"workflow","runtime":"cursor-native","title":"thermo-nuclear-review","description":"Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$ca","rawMarkdown":"$cb","relatedFiles":[]},{"id":"thermos","packId":"thermos","packName":"Thermos","kind":"workflow","runtime":"cursor-native","title":"thermos","description":"Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.","authorName":"Cursor","authorUrl":"https://cursor.com","body":"$cc","rawMarkdown":"$cd","relatedFiles":[]}],"skillPacks":[{"id":"agent-compatibility","displayName":"Agent Compatibility","version":"1.0.0","description":"CLI-backed repo compatibility scans plus agents that audit startup, validation, and docs against reality.","author":"Cursor","authorUrl":"https://cursor.com","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/agent-compatibility","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://github.com/cursor/plugins/tree/main/agent-compatibility","defaultRuntime":"cursor-native"},{"id":"cli-for-agent","displayName":"CLI for Agents","version":"1.0.0","description":"Patterns for designing CLIs that coding agents can run reliably: non-interactive flags, layered help with examples, pipelines, actionable errors, idempotency, and dry-run.","author":"Cursor","authorUrl":"https://cursor.com","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/cli-for-agent","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://github.com/cursor/plugins/tree/main/cli-for-agent","defaultRuntime":"portable"},{"id":"continual-learning","displayName":"Continual Learning","version":"1.0.0","description":"Incrementally learns durable user preferences and workspace facts from transcript changes and keeps AGENTS.md up to date with plain bullet points.","author":"Cursor","authorUrl":"https://cursor.com","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/continual-learning","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://github.com/cursor/plugins","defaultRuntime":"cursor-native"},{"id":"create-plugin","displayName":"Create Plugin","version":"1.0.0","description":"Scaffold and validate new agent plugins. Handles directory setup, manifest generation, and pre-submission quality checks for the marketplace.","author":"Cursor","authorUrl":"https://cursor.com","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/create-plugin","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://github.com/cursor/plugins","defaultRuntime":"cursor-native"},{"id":"cursor-team-kit","displayName":"Cursor Team Kit","version":"1.2.0","description":"Internal engineering team workflows for CI, code review, shipping, control-cli, control-ui, verify-this, test reliability, code cleanup, and work summaries. Designed to work without requiring third-party service integrations.","author":"Cursor","authorUrl":"https://cursor.com","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/cursor-team-kit","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://github.com/cursor/plugins","defaultRuntime":"cursor-native"},{"id":"orchestrate","displayName":"Orchestrate","version":"1.1.0","description":"Fan a large task out across parallel cloud agents via the Cursor SDK: planners publish tasks, workers hand off back up, and a script reconciles the tree from disk and git.","author":"Cursor","authorUrl":"https://cursor.com","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/orchestrate","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://github.com/cursor/plugins/tree/main/orchestrate","defaultRuntime":"cursor-native"},{"id":"pstack","displayName":"pstack","version":"0.14.5","description":"If you want to go fast, go deep first. Rigorous Cursor agent workflows you can parallelize with confidence.","author":"Lauren Tan","authorUrl":"https://github.com/poteto","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/pstack","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://cursor.com/marketplace/cursor/pstack","defaultRuntime":"$undefined"},{"id":"ralph-loop","displayName":"Ralph Loop","version":"1.0.0","description":"Continuous self-referential AI loops for iterative development, implementing the Ralph Wiggum technique. Run the agent in a while-true loop with the same prompt until task completion.","author":"Cursor","authorUrl":"https://cursor.com","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/ralph-loop","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://github.com/cursor/plugins","defaultRuntime":"cursor-native"},{"id":"teaching","displayName":"Teaching","version":"1.0.0","description":"Skill mapping, practice plans, and learning retrospectives. Builds personalized roadmaps with milestones and practice checkpoints, and runs periodic reviews to adjust based on progress.","author":"Cursor","authorUrl":"https://cursor.com","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/teaching","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://github.com/cursor/plugins","defaultRuntime":"portable"},{"id":"thermos","displayName":"Thermos","version":"1.0.0","description":"Thermo-nuclear branch review: deep correctness and security audits plus harsh code-quality rubrics, parallel subagents, thermos orchestration, and optional take-the-wheel and FSD merge-ready flows.","author":"Cursor","authorUrl":"https://cursor.com","license":"MIT","sourceUrl":"https://github.com/cursor/plugins/tree/main/thermos","repository":"https://github.com/cursor/plugins","sourceCommit":"fd878692de15a3069c21c8f429eb0b9f2fe178fa","homepage":"https://github.com/cursor/plugins","defaultRuntime":"cursor-native"}]}]

Your Personal Prompt Library

No Saved Prompts Yet