FradSer
- 132 skills
- 0 followers
- 580 repo stars
- 2 weeks ago last updated
- ▌ Writing For Agents · fradser bundleWriting documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
- ▌ Verification Before Completion · fradserUse 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.
- ▌ Request Refactor Plan · fradserCreate a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
- ▌ Setup TS Deep Modules · fradser bundleWires 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.
- ▌ Writing Great Skills · fradser bundleReference 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.
- ▌ Setup Matt Pocock Skills · fradser bundleConfigures a repo for the engineering skills — issue tracker, triage label vocabulary, and domain doc layout. Use once before first use of the other engineering skills, when the user says "set up the skills" or "initialize repo config".
- ▌ Delegate · fradser bundleDelegates 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.
- ▌ Storm Write · fradserRun 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.
- ▌ Storm Engine · fradserProvides 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.
- ▌ Storm Polish · fradserRun 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.
- ▌ Acpx · fradser bundleUse acpx as a headless ACP CLI for agent-to-agent communication, always inside an isolated SubAgent. Use when running coding agents through acpx, managing persistent ACP sessions, queueing prompts, consuming structured agent output from scripts, comparing the same prompt across multiple agents, or composing multi-agent workflows with defineFlow/decision/decisionEdge. Never invoke the claude adapter (nested-instance blacklist).
- ▌ Tropes · fradser bundleDetects 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.
- ▌ Storm Outline · fradserRun 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.
- ▌ Init · fradserInitializes or optimizes git-agent configuration, regenerates commit scopes from git history, and re-derives .gitignore rules.
- ▌ Storm Generate · fradserRun 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.
- ▌ Storm Research · fradserRun 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.
- ▌ Remotion · fradser bundleProgrammatic 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 getting media metadata. Do NOT use for ffmpeg-only pipelines, video.js/players, WebRTC live streaming, framer-motion web animation, or After Effects.
- ▌ Start Hotfix · fradserBegins a hotfix for a production issue using git-flow. This skill should be used when the user asks to "start a hotfix", "create hotfix branch", "fix a critical bug", "git flow hotfix start", or wants to begin a hotfix. Accepts either an explicit version or a natural-language description of the fix.
- ▌ Create Pr · fradser bundleCreates comprehensive GitHub pull requests with automated quality validation and security scanning, then hands off to /github:review-pr for CI monitoring and reviewer-comment triage. This skill should be used when the user asks to "create a PR", "submit a pull request", or needs to merge completed work with full compliance checks.
- ▌ Review Pr · fradser bundleReviews a pull request: runs its own baseline review of the PR diff, then a persistent Monitor watches CI and incoming reviewer comments, triages each comment through an independent skeptical agent, applies only verified fixes, and commits+pushes via inline git commands until CI passes and no comments remain to adopt — then asks whether to merge. Use this skill when the user asks to "review a PR", "monitor PR review comments", "address reviewer feedback on #123", or "watch CI on a pull request".
- ▌ Related · fradserMines git history to find files and test suites that historically change together with specified target files (co-change relations). Use before making changes or running tests to discover coupled code.
- ▌ Finish Hotfix · fradserFinalizes a hotfix and merges it into main and develop using git-flow, then prunes stale branches and worktrees. This skill should be used when the user asks to "finish a hotfix", "merge hotfix branch", "complete hotfix", "git flow hotfix finish", or wants to finalize a hotfix.
- ▌ Start Feature · fradserStarts working on a new feature branch using git-flow. This skill should be used when the user asks to "start a feature", "create feature branch", "begin new feature", "git flow feature start", or wants to start a new feature. Accepts either a branch name or a natural-language description.
- ▌ Start Release · fradserBegins a new version release using git-flow. This skill should be used when the user asks to "start a release", "create release branch", "prepare a release", "git flow release start", or wants to begin a new version release. Accepts either an explicit version or a natural-language description of the release.
- ▌ Create Prd · fradser bundleThis skill should be used when the user asks to "create PRD", "write product requirements document", or mentions "PRD", "product requirements document".
- ▌ Refactor · fradser bundleExecutes 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".
- ▌ Lark · fradser bundleLark/Feishu CLI router: match intent, then Read the Entry file under lark-*/ (e.g. lark-doc/lark-doc.md). Covers docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, note, event via lark-cli. Use when operating Feishu/Lark workspace resources, messaging, docs, calendars, tasks, OKRs, or Miaoda deploys.
- ▌ Setup · fradserGuides 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.
- ▌ Marketing · fradser bundleMarketing skills router: match marketing intent to a sub-skill, then Read its Entry file under skills/<name>/ (e.g. ads/ads.md). Covers CRO, copywriting, SEO/AEO, paid ads, ad creative, analytics, email/SMS, pricing, launches, video/image generation, and growth loops. Use for any marketing request — campaigns, content, optimization, measurement.
- ▌ Review · fradser bundleReviews 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.
- ▌ Commit · fradserCreates clean, conventional git commits using standard git. Use when the user asks to "commit", "git commit", "create commit", or wants to commit staged or unstaged changes.
- ▌ Hyperframes · fradser bundleREAD THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic — a promo, explainer, captioned clip, title card, overlay, slideshow / interactive deck, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames domain skills, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework.