All authors
Claude Skills by FradSer
github.com/FradSer100 skills5 installs168 views
- Claude HandoffHands the current conversation to a fresh background agent that picks up the work immediately. Use when the user wants the work continued by a background agent.Votes: 0GitHub stars: 593
- Loop MeRuns a stateful grilling session that produces workflow specs for workflows the user wants to build. Use when the user says \"loop me\" or wants workflow specs drawn out of them.Votes: 0GitHub stars: 593
- Setup Ts Deep ModulesWires dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through entry-point files. Use when the user wants deep-module enforcement or dependency-cruiser setup.Votes: 0GitHub stars: 593
- Writing BeatsExploit-phase writing — assembles raw material into a journey of beats, grounding each term before a beat leans on it. Use when the user has raw material and wants it turned into an article.Votes: 0GitHub stars: 593
- Writing FragmentsExplore-phase writing — mines raw fragments without committing to structure. Use when the user wants to brainstorm material or gather fragments for a later article.Votes: 0GitHub stars: 593
- Writing ShapeExploit-phase writing — shapes raw material into an article paragraph by paragraph. Use when the user has a raw-material pile and wants the final article written.Votes: 0GitHub stars: 593
- Grill MeRuns a relentless interview that sharpens a plan or design. Use when the user wants to be grilled on an idea, pressure-test a plan, or refine a design through questioning.Votes: 0GitHub stars: 593
- GrillingGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.Votes: 0GitHub stars: 593
- HandoffCompacts the current conversation into a handoff document for another agent to pick up. Use when the user says \"hand this off\" or wants the work continued by a fresh session.Votes: 0GitHub stars: 593
- TeachTeaches the user a new skill or concept within the workspace. Use when the user says \"teach me X\", wants to learn a topic over sessions, or needs a structured learning plan.Votes: 0GitHub stars: 593
- To QuestionnaireTurns a decision the user can't fully answer into a questionnaire for someone else to fill in. Use when the user says \"turn this into a questionnaire\" or needs knowledge pulled out of an expert.Votes: 0GitHub stars: 593
- Wait WhatStop. That last message did not land: re-pitch it. Use when the user says \"wait what\", \"I don't follow\", \"explain that again\", or similar confusion signals.Votes: 0GitHub stars: 593
- Writing Great SkillsReference for writing and editing skills well — the vocabulary and principles that make a skill predictable. Use when the user asks \"how should I write a skill\" or wants skill-writing best practices.Votes: 0GitHub stars: 593
- ConsolidateConsolidates project memory across harness and .memory/ with theme clustering, practical-expiry prune, ground-truth verify, and an adversarial second pass. Use when the user runs /memory:consolidate, asks to tidy/dedupe/prune memory, or reports redundant or stale memories. Also covers active writing during work.Votes: 0GitHub stars: 593
- Create PrdThis skill should be used when the user asks to "create PRD", "write product requirements document", or mentions "PRD", "product requirements document".Votes: 0GitHub stars: 593
- Generate VideoGenerate short videos from a text prompt or from still images using ByteDance Seedance on Volcengine Ark. Use this skill whenever the user wants to create, generate, render, or animate a video, clip, animation, motion graphic, or product demo — including text-to-video ("a drone shot over a forest at sunrise") and image-to-video, where a still becomes the first frame, or two stills are morphed start-to-end. Prefer this skill over describing a video in text.Votes: 0GitHub stars: 593
- Patent ArchitectAutomatically searches prior art via SerpAPI and generates Chinese patent application forms. This skill should be used when the user wants to generate Chinese patent application forms, or mentions "patents", "inventions", or wants to protect technical innovations.Votes: 0GitHub stars: 593
- RemotionProgrammatic video creation in React with Remotion. Use this skill whenever the user writes Remotion, npx create-video, remotion studio/render/still, useCurrentFrame/interpolate/Sequence, Composition, Mediabunny, or any React-driven video/animation/caption/motion-graphics task — including scaffolding a project, writing markup, rendering/exporting (incl. transparent), adding captions/subtitles, making Studio-editable animations, building a Remotion SaaS (Player/Lambda/Vercel/Cloudflare), or ge...Votes: 0GitHub stars: 593
- TropesDetects and eliminates AI writing tropes that make text sound artificial or formulaic. Use when generating text content, writing documentation, creating code comments, or reviewing writing style. Supports four-tier JSON preferences (global/project x shared/local office.json) read via load-preferences.sh.Votes: 0GitHub stars: 593
- DelegateDelegates a coding task to pi (dev/pi), a minimal terminal coding harness. This skill should be used when the user asks to "use pi", "run pi", "delegate to pi", "let pi handle this", "ask pi to", "have pi do", or invokes /pi:delegate. It bridges the current Claude Code context to the pi CLI, passing relevant files, git state, and the task description for execution by the pi-agent.Votes: 0GitHub stars: 593
- ReviewReviews code using pi CLI with read-only tools. Delegates the review to pi (dev/pi) with a structured review rubric, running in read-only mode to prevent accidental edits. By default reviews uncommitted working tree changes (git diff HEAD) with pi restricted to the read tool; explicit targets (--branch/--diff/@file/PR) or --explore widen pi to read,grep,find,ls. Use when the user asks to "review code with pi", "pi review", "have pi review", "let pi review", or invokes /pi:review.Votes: 0GitHub stars: 593
- SetupGuides the user through configuring pi — provider, model, base URL, and API key. Use when the user asks to "setup pi", "configure pi", "pi setup", "set up pi provider", "pi config", "change pi model", or invokes /pi:setup. Only run this skill when the user explicitly requests pi setup — never auto-invoke.Votes: 0GitHub stars: 593
- Examples**Purpose**: Execute tasks when user invokes via `/command` or direct skill call. **Frontmatter Requirements**: ```yaml --- name: skill-name description: Execute this when user requests [workflow/task description] user-invocable: true allowed-tools: ["Read", "Glob", "Bash(git:*)", "Task", ...] --- ``` **Writing Style Requirements**: - Use imperative voice: "Load...", "Create...", "Analyze...", "Execute..." - Never use declarative descriptions: avoid "is", "are", "provides" **Structure Require...Votes: 0GitHub stars: 593
- Examples**Purpose**: Provide background knowledge for agents. **Frontmatter Requirements**: ```yaml --- name: skill-name description: Provides [knowledge type] for [domain/purpose] user-invocable: false --- ``` **Writing Style Requirements**: - Use declarative voice: "Skills are...", "Components provide...", "Use when..." - Never use imperative commands: avoid "Load", "Create", "Execute" **Structure Requirements**: - Topic-based sections: "## Core Concepts", "## Best Practices", "## Patterns" - Use r...Votes: 0GitHub stars: 593
- Optimize PluginThis skill should be used when the user asks to "validate a plugin", "optimize plugin", "check plugin quality", "review plugin structure", or "run plugin optimizer".Votes: 0GitHub stars: 593
- Plugin Best PracticesThis skill should be used when the user asks to "validate plugin structure", "review manifest files", "check frontmatter compliance", "verify tool invocation patterns", "explain plugin component types", or needs Claude Code plugin architectural guidance.Votes: 0GitHub stars: 593
- Best PracticesLanguage-specific best practices, code quality standards, and framework detection rules. Use when executing refactoring workflows, applying code quality rules, detecting frameworks, or checking language-specific patterns for TypeScript, Python, Go, Swift, or React.Votes: 0GitHub stars: 593
- Refactor ProjectExecutes automated project-wide refactoring with a focus on cross-file optimization. This skill should be used when the user asks for project-wide refactoring, cross-file simplification, consistency standardization across the codebase, duplication reduction, or invokes "/refactor-project".Votes: 0GitHub stars: 593
- RefactorExecutes automated refactoring for specific files, directories, or semantic queries. This skill should be used when the user asks to refactor specific files or directories, simplify recently changed code, clean up dead code in a limited scope, or invokes "/refactor".Votes: 0GitHub stars: 593
- EngineProvides the shared STORM methodology, artifact layout, stage-gating contract, citation hygiene, and retrieval fallback. Use when executing any /storm:* skill (generate, research, outline, write, polish). Internal knowledge; never user-invocable.Votes: 0GitHub stars: 593
- GenerateRun the full STORM pipeline end-to-end. This skill should be used when the user asks to "generate a storm article", "write a wikipedia-style article about X", "research and write a long-form piece on X", or invokes /storm:generate. Orchestrates research -> outline -> write -> polish, skipping already-completed phases.Votes: 0GitHub stars: 593
- OutlineRun STORM phase 2 — outline generation. This skill should be used when the user asks to "generate an outline for a storm article", "draft a wikipedia-style outline", or invokes /storm:outline. Produces a draft outline from parametric knowledge then refines it using the research information table.Votes: 0GitHub stars: 593
- PolishRun STORM phase 4 — article polishing. This skill should be used when the user asks to "polish the storm article", "finalize the article", or invokes /storm:polish. Adds a summary section, removes duplicate content, and verifies citation integrity.Votes: 0GitHub stars: 593
- ResearchRun STORM phase 1 — multi-perspective research. This skill should be used when the user asks to "research a topic for an article", "find sources on X from multiple perspectives", "do storm research on X", or invokes /storm:research. Discovers personas, runs simulated Q&A per persona in parallel, and produces an information table + deduplicated sources.Votes: 0GitHub stars: 593
- WriteRun STORM phase 3 — per-section article writing. This skill should be used when the user asks to "write the article sections", "draft the storm article", or invokes /storm:write. Writes each outline section in parallel with inline citations grounded in the research sources.Votes: 0GitHub stars: 593
- Behavior Driven DevelopmentApplies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.Votes: 0GitHub stars: 593
- BrainstormingDesigns new software features and multi-component changes for the current repo into implementation-ready BDD specs via autonomous codebase research, then commits the design for review (runs to completion without mid-design questions). Scope covers new features, greenfield design, and multi-component changes. Not for hardware/physical-system design, out-of-repo questions, single-file refactors, or known-root-cause bugs (those go to direct edits or systematic-debugging).Votes: 0GitHub stars: 593
- Executing PlansExecutes a written implementation plan via per-batch sub-agent coordinators with verification and commits between batches.Votes: 0GitHub stars: 593
- Receiving Code ReviewUse when the superpowers-evaluator returned REWORK on a batch, when fixing rework items from an evaluation report, or when receiving any code review feedback on superpowers output. Requires technical rigor and verification instead of performative agreement or blind implementation.Votes: 0GitHub stars: 593
- RetrospectiveAnalyzes evaluation patterns across completed plans and evolves the superpowers checklists accordingly.Votes: 0GitHub stars: 593
- Systematic DebuggingDiagnoses a reported bug, error, test failure, or unexpected behavior through a 4-phase root-cause analysis before any code changes.Votes: 0GitHub stars: 593
- Verification Before CompletionUse when about to claim work is complete, fixed, or passing, before committing, before reporting a task done, or before telling the evaluator the batch is ready. Requires running the verification command and reading its output in this turn before any success claim; evidence before assertions always.Votes: 0GitHub stars: 593
- Writing PlansCreates executable implementation plans that break down a brainstorming design into detailed, unambiguous per-batch tasks for execution.Votes: 0GitHub stars: 593
- Swiftui ReviewReviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.Votes: 0GitHub stars: 593
- Update ChangelogCreates or updates CHANGELOG.md following the Keep a Changelog 1.1.0 format. Use this skill when the user asks to "update the changelog", "generate changelog", "add changelog entry", "create CHANGELOG.md", "sync changelog with tags", or wants to document project changes based on git tags and commit history.Votes: 0GitHub stars: 593
- Update ReadmeUpdates README.md and README.zh-CN.md to reflect the project's current state. Use this skill whenever the user asks to "update the README", "sync the docs", "update documentation", "reflect latest changes in README", or wants both the English and Chinese READMEs to match the current project.Votes: 0GitHub stars: 593
- Reflect Skills From MemoryThis skill should be used when the user asks to "reflect on skills from memory", "audit marketplace skills against memory", "从记忆中检查 skills 的问题", "反思并修改 skill", "apply memory feedback to skills", or wants to turn accumulated memory feedback about this marketplace's skills into concrete skill fixes. Reads the project's persistent memory, re-verifies each known skill problem against current code, then fixes the skill or corrects the stale memory.Votes: 0GitHub stars: 593
- Implement SpecImplement a specification in code.Votes: 0GitHub stars: 593
- Setup Pre CommitSet up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.Votes: 0GitHub stars: 593
- Edit ArticleEdit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.Votes: 0GitHub stars: 593