AI Agent Workflow Collection

Packaging and go-to-market hydration skill. Takes DoU audit findings and executes the non-code work that bridges the gap between "it works" and "someone can buy this." Generates marketplace listings, SEO fixes, distribution artifacts, onboarding flows, landing page content, and representation surfaces for products that do not naturally have a public web UI. Trigger phrases: "hydrate", "package for market", "prepare for launch", "przygotuj do launchu", "fix the packaging gap", "marketplace listing", "nawodnij", "make it shippable", "go-to-market", "distribution", "SEO fix", "landing page", "onboarding", "completion sprint".

Technical due diligence before stabilization. The vibe-coding weekend got the app to launch. Now we find the taped-together auth, god tables, and silent failures. Init equips the agent with Perception (via the MCP-first loctree context engine), Intentions (AICX), and Security/Stability Ground Truth. Trigger: "init", "initialize", "bootstrap", "daj kontekst", "zainicjuj", "przygotuj agenta", "start fresh with context".

WRITE step that floods every crack with deliberate over-correction. Single workers see one round, one truth-forcing cut, one commit; the skill at swarm level produces an intentional excess of fixes — marbles in every hole — which vc-polarize then strips back to one axis. Use when implementation already exists but the codebase still lies: overgenerated surfaces, drift between runtime paths, false certainty from one-shot agent output, or a product that "works" while remaining fragile. Each worker invocation is isolated and blind to prior marble history. Trigger phrases: "marbles", "kulki", "stabilize", "stabilizacja", "loop until done", "reduce chaos", "fortify the foundation", "adultification", "rzuć kulki", "wypełnij pęknięcia".

Full-spectrum VetCoders ownership mode for moments when the user wants Agent to take the wheel and drive a product from A to Z: architecture, coding, runtime debugging, UI polish, packaging, docs, testing, local tooling, agent orchestration, and wow-effect finish. Use whenever the user says things like "take ownership", "you drive", "od a do z", "zrob to cale", "dowiez to", "wow effect", "superprodukcyjny", "manufakturer produktowy", or when the team clearly wants decisive end-to-end execution with minimal back-and-forth. This skill is intentionally pushy: if the user is asking for total delivery, use it even when they do not explicitly name the skill.

WRITE step that strips back the marbles excess to one truth. Where the swarm of marble workers plastered every crack in deliberate over-application, polarize picks one axis, rejects the competing ones, and aligns runtime, tests, docs, artifacts, and public promises so they all agree. Gated on Loctree loct prism bands — 0..4 abort, 5..8 memo, 9..12 pass, 13..15 doctrine. Emits DoU / release handoff. Trigger phrases: "polarize", "vc-polarize", "wyostrz", "one sharp truth", "code smear", "prism score", "after marbles", "choose one axis", "decisive cut".

Final outward ship skill. Turns "done in the repo" into "safe, visible, deployable, discoverable, and launchable in the world." Covers release mechanics, deployment topology, reverse-proxy defaults, Semgrep-gated security hygiene, domain and DNS wiring, SEO/indexability, verification challenges, onboarding truth, and post-release smoke checks. Trigger phrases: "release", "ship to market", "publish", "deploy to production", "vc-release", "go live", "launch", "wypuść wersję", "deploy", "release prep", "launch path", "launch checklist", "production checklist".

ScreenScribe workflow skill for analyzing screencast recordings and for working inside the ScreenScribe repo itself. Use this whenever the user mentions ScreenScribe, screencast review, app review videos, bug demo recordings, HTML Pro reports, transcript-first artifact extraction, extracting actionable findings from narrated videos, batch video analysis, or wants to debug/build/improve the ScreenScribe project or the default https://github.com/VetCoders/Screenscribe repository. Prefer this skill even if the user does not explicitly ask for "ScreenScribe" but clearly wants a spoken screen recording turned into structured engineering findings.

Distills a completed user workflow, session interaction or pattern into a reusable agent skill. Use when the user asks to turn their workflow, interaction, or multi-step process into a skill, or when they say "make this a skill", "create a skill from what we just did", "package this workflow" or similar. Do not use for creating skills from scratch without an existing workflow (use a generic skill-creator for that).

Meta-doctrine for human taste, agent force, Loctree/AICX structure, and reality-tested shipping posture.