hungv47

brief-app-preview

Produces production-ready briefs for app onboarding, App Store preview, and feature-demo videos from supplied UI screenshots. Defines the feature promise, cropped UI beats, interaction choreography, captions, motion rules, platform specs, and asset manifest. Use when screenshots exist and the goal is to show a product feature in action. Not for generic short-form social videos (use brief-shortform) or rendering the video (use produce-video).

brief-graphic

Produce a graphic-design brief for a single visual asset — social posts, thumbnails, banners, OOH, OG cards, hero illustrations. Pulls brand tokens, generates concepts, writes platform-aware specs + image-gen prompt or designer-handoff spec. Does NOT render — rendering is downstream. Not for brand identity (use create-brand), whole-page redesigns (use brief-landing-page), or the copy that goes IN the asset (use write-copy).

Web & Frontend Listed

brief-landing-page

Generates a campaign-grade brief for a conversion landing page or redesign — hypothesis, surface rhythm, section-by-section spec, asset slots, copy candidates, hand-off prompts, conversion + brand-voice critics. Output ready for Claude Design, Figma, a human designer, or a coding agent. Not for post-launch CRO from analytics (use evaluate-landing-page inside an eval-loop), non-conversion pages (blogs, docs), or a single visual asset (use brief-graphic).

brief-shortform

Production-ready brief for short-form video — hook, shot list, on-screen text, audio plan, caption, CTA, aspect, length. Covers live-action + motion-graphic. 1 hero + max 2 variants per run. Reads the per-platform research-shortform catalog. Not for static visual assets (use brief-graphic), organic social copy (use write-social), paid ad creative (use write-ad), or rendering (use produce-video).

create-brand

Builds a brand identity system as up to three artifacts — BRAND.md (story, voice, positioning, archetype), DESIGN.md (AI-readable design tokens), ASSETS.md (per-platform inventory). Runs Quick Brand (Route A) or full brand-system (Route B). Use to define or rebrand a product's identity. Not for marketing copy (use write-copy), user flows (use map-user-flow), campaign planning (use plan-campaign), or audience research (use research-icp).

evaluate-ad

Score a launched Meta ad from real metrics (CTR, CPA, ROAS, frequency, fatigue, spend) inside an existing eval loop — verdict + diagnosis + creative-fatigue signals. One cycle per audience-temp. Meta-only at v1. Not for loop setup (use run-eval-loop), writing new creative (use write-ad), channel-mix retrospectives (use plan-campaign), or campaign-level scoring (use evaluate-campaign).

evaluate-campaign

Score a launched multi-channel campaign from real metrics inside an existing eval loop — verdict, per-channel breakdown, unit economics. Aggregate-only: one cycle = whole campaign, all channels. Requires an eval-loop workspace. Not for loop setup (use run-eval-loop), re-planning (use plan-campaign), or per-asset eval — single ad uses evaluate-ad, post evaluate-content, page evaluate-landing-page, short-form evaluate-shortform.

evaluate-content

Score a published organic post (text / image / carousel) from real metrics inside an existing eval loop — one primary platform per cycle, verdict + engagement-quality diagnosis. Not for short-form video (use evaluate-shortform), paid-ad performance (use evaluate-ad), writing next-cycle copy (use write-social), or scaffolding the loop (use run-eval-loop).

Web & Frontend Listed

evaluate-landing-page

Scores a launched landing page from real performance evidence inside an existing eval loop. Writes a cycle eval snapshot and appends the loop results ledger. Use for post-launch CRO cycles backed by analytics, experiment results, recordings, form-funnel data, or qualified manual metric notes. Not for designing the next page brief or a redesign (use brief-landing-page), channel-strategy questions (use plan-campaign), generic best-practice audits without measurement evidence, or scaffolding the loop itself (use run-eval-loop).

humanmaxxing

Strip AI tells, inject brand voice, and compress existing text so it reads human-written — 15%+ word reduction with zero idea loss + optional detector-resistance pass. Use as a terminal polish pass on AI-drafted copy that sounds robotic. Not for writing new copy from scratch (use write-copy); for brand voice of record see create-brand.

monitor-aeo

Monitors AI-search visibility across answer engines and generative-search surfaces — provider/query citation checks, Google AI Overview/GEO citation presence, Bing/IndexNow readiness, AI referral traffic, llms.txt status, competitor cited-domain share, and dated snapshot reports. Use when you need evidence of whether AI systems mention or cite a brand/site. Not for deciding SEO strategy or rewriting pages (use optimize-seo) and not for technical-audit remediation.

optimize-seo

Audits and plans search visibility across six modes — technical SEO audit, AI/answer-engine optimization (AEO), programmatic SEO, competitor comparison pages, full SEO strategy, and app store optimization (ASO). Covers keyword research, on-page and technical fixes, link-building strategy, and structured data. Use to diagnose a traffic drop, plan search growth, or get found by AI search. Not for landing-page conversion brief work (use brief-landing-page) or writing the page copy (use write-copy).

plan-campaign

Builds an integrated marketing plan — growth motion, messaging pillars, per-channel angles across all 9 channels, content calendar, budget allocation, and a phased go-to-market timeline. Use when you need a campaign strategy or GTM plan grounded in ICP research. Not for setting numeric funnel targets (use plan-funnel), search-channel strategy (use optimize-seo), or landing-page architecture (use brief-landing-page).

polish-vn

Polishes already-translated Vietnamese text so it reads natively in a target register (báo chí, semi-casual, bro, or pop-marketing) — fixes pronoun drift, missing particles, literal idioms, passive-voice calques, typography, and corporate translationese. Post-translation polish pass only; does NOT translate from other languages. Use on translated Vietnamese copy that reads stiff or foreign. Not for tone work on English or other languages (use humanmaxxing), or writing new Vietnamese copy from scratch (use write-copy).

produce-asset

Turns a brief-graphic artifact into render-ready prompts + an asset manifest. Tool-agnostic by design — emits prompts tuned for your chosen image engine (Midjourney / DALL·E / Imagen / Figma / designer); the stack holds no API keys and runs no render engines. Use when a design brief exists and you need production-ready prompts. Not for the copy that goes in the asset (use write-copy), the brief itself (use brief-graphic), or publishing the rendered asset (use publish-social).

produce-video

Turn a brief-shortform or brief-app-preview into a multi-runtime export bundle — manifest, per-shot prompts, HyperFrames + Remotion scaffolds, Vercel AI CLI README. Two modes: shortform (social/promo) and app-preview (screenshot-driven product demo). Tool-agnostic — emits scaffolds + prompts; does NOT invoke render engines. Not for writing the brief (use brief-shortform / brief-app-preview) or publishing (use publish-social).

publish-social

Turn write-social copy into a publishing bundle — per-platform drafts plus scheduler-import files (Typefully / Buffer / Hootsuite / CSV). `--mode=publish` posts live behind a two-stage gate. Covers 9 platforms (X / LinkedIn / Instagram / YouTube / TikTok / Facebook / Bluesky / Threads / Reddit). Not for writing copy (use write-social), media generation (use produce-asset / produce-video), or landing-page placement.

write-ad

Writes and evaluates Meta paid-ad copy (retargeting + cold-traffic) — audience-temperature-aware framing, hard char-cap enforcement, policy compliance, 7-dim rubric. Meta-only at v1. Not for landing-page headlines (use write-copy), cold-outreach DMs (use write-outreach), organic social posts (use write-social), or channel-mix strategy (use plan-campaign).

write-copy

Writes and evaluates persuasive copy — headlines, hooks, CTAs, taglines, and landing-page sections — with per-line V/F/U rubric scoring, annotations, and ranked alternatives. Not for AI-sounding cleanup (humanmaxxing), search/AI-citation (optimize-seo), brand voice (create-brand), landing-page architecture (brief-landing-page), social posts (write-social), or paid-ad copy (write-ad).

write-outreach

Writes and evaluates cold outreach — email, LinkedIn, Twitter/X, iMessage/SMS, platform proposals — with signal-based personalization, channel-specific craft, and rubric scoring. Handles first-touch compose and reply-to-inbound modes. Use to draft or critique an individual outbound message. Not for campaign orchestration or sequence design (use plan-campaign), landing-page or headline copy (use write-copy), paid-ad copy (use write-ad), or sourcing/list-building. Brand voice: see create-brand.

write-social

Platform-native social copy (hook variants + body + CTA + format spec) for tiktok, reels, shorts, x, linkedin. Single-platform per artifact. 5-dim rubric. Not for paid-ad copy (use write-ad), landing-page copy (use write-copy), short-form video briefs with storyboards (use brief-shortform), or long-form articles. Vietnamese polish: polish-vn. AI-tell cleanup: humanmaxxing.

breakdown-tasks

Decomposes a spec or architecture into buildable tasks with acceptance criteria, dependencies, and risk-first implementation order, for AI agents or human engineers. Produces `.forsvn/artifacts/meta/tasks.md`. Use once requirements are clear and you need an execution plan. Not for clarifying unclear requirements (use discover) or designing architecture (use architect-system). For code review after building, see review-work.

clean-artifacts

Audit + groom `.forsvn/artifacts/` — classify every file (KEEP/STALE/ORPHAN/LEGACY/EPHEMERAL), surface references + risk. On `--apply` archives candidates behind per-category confirmation (moves to dated archive, never deletes). Not for cleaning code (use clean-code) or machine state (use clean-machine).

debate-agents

Runs a problem through multiple expert perspectives via debate (agents argue in rounds and converge) or poll (agents analyze independently, then aggregate by consensus). Use to pressure-test a decision or trade-off with no clear winner. Standalone, or invoked by another skill as a sub-routine. Not for implementation (use architect-system) or code verification (use review-work).

discover

Conversational discovery that turns a vague idea, feature, or task into shared clarity — adapts from quick scoping (3-5 questions) to deep multi-round interviews, then produces inline decisions or an optional saved spec. Use to clarify requirements before building. Not for multi-perspective debate (use debate-agents), decomposing work (use breakdown-tasks), or diagnosing a metric decline (use diagnose).

forsvn

Front door for the FORSVN agent stack — classifies the request, loads shared product context and prior session state, then routes to the right skill or resumes a prior initiative. Use when you don't know which skill to call, want to continue something you started, or a vague ask needs to land somewhere concrete ("where do I start", "resume", "ship this").

review-work

Independent post-implementation review — an agent with no sunk-cost bias checks just-written code or an artifact against its requirements, then resolves the issues found (max 2 rounds). Use to verify a change before shipping, get a second opinion, or check what you missed; auto-triggers for security-sensitive and data-mutation code. Not for code refactoring (use clean-code) or decision analysis (use debate-agents).

run-eval-loop

Scaffolds and maintains the workspace for a measurable strategy → execution → evaluation cycle — creates `.forsvn/loops/[slug]/` with program, context, a results ledger, and learnings. Use for an improvement loop, experiment ledger, or campaign/content iteration system tied to a metric. Routes surface scoring to the matching evaluate-* skill; not a universal evaluator. Not for one-shot planning (use discover or breakdown-tasks) or multi-perspective debate (use debate-agents).

architect-system

Designs technical blueprints — tech stack selection, database schema, API design, file structure, and deployment plan for a defined product or feature. Produces `architecture/system-architecture.md`. Not for unclear requirements (use discover) or task decomposition (use breakdown-tasks). For user journey mapping, see map-user-flow. For code quality after building, see review-work.

clean-code

Audits and refactors existing code for readability, maintainability, and dead code removal without changing behavior. Produces `.forsvn/artifacts/meta/records/[date]-cleanup-<slug>.md` and applies fixes in-place. Not for diagnosing business problems (use diagnose) or writing documentation (use write-docs). For writing missing docs after cleanup, see write-docs.

clean-machine

Audit + clean a developer's machine — dotfolders, caches, language toolchains, package globals — with per-target classification, risk surfacing (auth, processes, side effects), and explicit confirmation. Produces `.forsvn/artifacts/meta/records/machine-cleanup-*.md`. Not for cleaning code (use clean-code) or for triaging user files (those need human review).

Data & Documents Listed

extract-service

Extracts repeated operational mechanics (SDK, API, file-system, or network logic copy-pasted across handlers or actions) into a shared service layer — produces a stepwise migration plan, then applies it caller-by-caller with verification at each step. Use when the same "how" recurs across 2+ callers. Not for behavioral cleanup or dead code (use clean-code) or designing a system from scratch (use architect-system). For a quality review after migrating, see review-work.

map-user-flow

Maps multi-step in-product flows — screens, decisions, transitions, platform-native touchpoints (dock, menu bar, widgets, notifications, Live Activity), edge cases, and error states for a feature or user journey. Use when designing or auditing a feature spanning multiple screens, states, or platforms. Not for visual brand design (use create-brand), landing-page architecture (use brief-landing-page), or technical architecture (use architect-system).

write-docs

Generate documentation from a codebase — READMEs, API references, setup guides, runbooks, architecture docs, ship logs, release notes (CHANGELOG + GitHub Release bodies). Not for specifying what to build (use discover), restructuring code (use clean-code), or task decomposition (use breakdown-tasks).

diagnose

Structured diagnosis of business and strategic problems — builds MECE logic trees, forms testable If/Then/Because hypotheses, scans external factors, and identifies root causes with evidence. Use when a metric is underperforming, something went wrong, or you need to find what's actually causing a problem before acting. Not for code bugs (use clean-code), brainstorming solutions to a known problem (use prioritize), or scoping a new idea (use discover). For market-level trends and competitive context, see research-market.

API & Backend Listed

evaluate-shortform

Closes the feedback loop for short-form video — scores a published post against its original brief and the matching short-form platform-intelligence catalog on a 4-dimension rubric, then logs a falsifiable pattern entry to the eval loop. Use to review a post after publishing, check whether a brief survived contact with the platform, or run an eval cycle inside an existing loop. Not for pre-publish brief authoring (use brief-shortform) or catalog discovery (use research-shortform). Needs an existing loop workspace — for that, see run-eval-loop.

plan-funnel

Models business funnels with numeric targets — works backward from a revenue goal to the required traffic, conversion rates, and unit economics, with every target carrying a baseline and justification. Use to set growth targets, model an LTV:CAC funnel, or check whether the numbers behind a plan actually work. Not for prioritizing what to build (use prioritize) or diagnosing a metric decline (use diagnose). For channel-level campaign planning, see plan-campaign.

prioritize

Brainstorms strategic solutions when the problem or goal is already clear — generates initiatives, force-ranks them, scores trade-offs with evidence-backed ICE, and draws a cut line with kill criteria. Use when you know the problem and need to decide what to build or pursue first. Not for diagnosing what the problem is (use diagnose) or engineering task lists (use breakdown-tasks). For numeric targets after prioritizing, see plan-funnel; for technical architecture of chosen initiatives, see architect-system.

research-icp

Builds ideal customer profiles and buyer personas from real voice-of-customer evidence — analyzes demographics, pain points, jobs-to-be-done, decision psychology, and online habitat for a target market. Use to define who you're talking to before messaging, channel, or positioning work. Foundational: its output feeds 13+ downstream skills. Not for competitive positioning (use prioritize) or campaign planning (use plan-campaign). For brand identity from audience data, see create-brand; for market sizing, see research-market.

research-market

Map market landscape, competitive dynamics, TAM/SAM/SOM sizing, whitespace opportunities — every claim sourced, adjacent competitors checked, sizing shown with methodology. Use to position a product, survey a competitive field, scope a new market, or build the market section of a fundraising deck. Not for personas (use research-icp), campaigns (use plan-campaign), problem diagnosis (use diagnose), or prioritization (use prioritize).

research-platform

Turns the operator's own platform evidence — owned analytics, public metrics, manual exports, qualitative observations, and prior eval outcomes — into a sourced per-platform evidence base across X, LinkedIn, TikTok, YouTube, and Instagram. Every metric is tagged with its evidence source and freshness; every recommendation names the platform, source, window, and confidence behind it. Use to ground social / SEO / short-form decisions in measured reality before briefing or publishing, or to refresh a stale evidence base. Not for discovering what's working in the wild (use research-shortform) or competitive / market sizing (use research-market). For audience research, see research-icp.

research-shortform

Discovers what's working right now on short-form video platforms (TikTok, Instagram Reels, YouTube Shorts; X and LinkedIn video by opt-in) for a given topic and market — mines hook archetypes, trending audio, and platform mechanics into a sourced per-platform catalog. Use before briefing short-form content, to find current viral patterns, or to refresh stale platform intelligence. Not for long-form video (parked) or static visuals (use brief-graphic). For audience research, see research-icp; for campaign planning, see plan-campaign.

build-ios-apps

Build, sign, install, and publish iOS apps using the Vibecode signing service. Use when the user wants to build an iOS app from source, sign an iOS app, install on their iPhone, register a device, set up Apple Developer auth, publish to the App Store or TestFlight, submit for review, or work with the iOS build/sign/distribute/publish pipeline. Also triggers for "test on device", "put this on my phone", "ship it to my iPhone", "publish to App Store", "submit my app", "push to TestFlight", "send for review", or any request to get a Swift/iOS app running on a real device or shipped to App Store Connect.