flow

Plugin flow in dork-labs/dorkos. Commands read from the repo's manifest — today.

Skills (44)

• auditing-ui

  Runs a lens-based UI/UX audit of the client and turns its findings into tracked, fenced work items, and measures the rendered page for a design review. Use when auditing the interface for quality gaps, running or scoping an audit (full, one lens, one surface, or a diff), driving the real-browser leg

• browser-testing

  Methodology for writing and maintaining DorkOS browser tests. Use when writing, running, debugging, or maintaining Playwright browser tests in apps/e2e, when deciding between a browser test and a unit test, or when e2e behavior needs verification.

• capturing-product-media

  Regenerate DorkOS product screenshots and video loops from the real UI, and manage the shot registry, human overrides, and version archives that feed the marketing site, docs, and changelogs. Use when marketing/docs media is stale after UI changes, a new feature or docs page needs a money shot, a pe

• ci-local-export

  Daily CI Steward job: export this clone's git hook timings (how long git commit and git push took, and which pushes were killed at the tool ceiling) to the ci-steward-data branch, then trim the local timings file. A DorkOS scheduled skill that runs pnpm ci:local-export.

• ci-pulse

  Collect CI Steward's pipeline numbers right now, locally, into a temporary directory, and show the ci-status screen from them, including this clone's local hook timings. Pushes nothing. Use when the daily snapshot is too old to answer the question.

• ci-quarantine

  Put a known-flaky test into, or take it out of, CI Steward's quarantine lane: it keeps running and reporting but cannot fail the merge queue. Use when a test that passes on retry keeps ejecting green PRs, when an entry is about to expire, or when a quarantined test is fixed and should block again.

• ci-status

  Show CI Steward's one-screen view of the pipeline: the SLO table, the one constraint to work on, the open improvement triggers, every ledger experiment with its computed verdict, and the collector's health. Reads the ci-steward-data branch; run it before changing CI or when asked how CI is doing.

• creating-pull-requests

  When to open a pull request in the DorkOS repo (review the pushed branch first, open the PR after it converges), how the automated review behaves (skip-review, review:light/deep, re-review), and how a PR lands through merge-tail and the merge queue, including what to do when it goes red or is ejecte

• debugging-systematically

  Guides systematic debugging methodology and troubleshooting approaches. Use when investigating bugs, tracing issues, or teaching debugging patterns.

• debugging-test-failures

  Systematically investigates failing tests, distinguishes between test bugs and implementation bugs, and drives a fix with verification. Use when the user wants to debug failing tests.

• debugging-typescript-errors

  Systematically investigates TypeScript compiler errors, traces the real type mismatch, and applies a minimal verified fix. Use when the user wants to debug TypeScript type errors.

• deps-weekly

  Monday DorkOS dependency upkeep, called from @dorkos-qa's heartbeat: runs /app:upgrade unattended in a throwaway worktree, lands one PR per lane, files tickets for majors, and posts one line to @dorkos-pm. Never bumps the runtime SDKs (that is runtime-watch). Use only when a heartbeat checklist or a

• designing-frontend

  Guides design thinking and decision-making for DorkOS UI, pointing at contributing/design-system.md for the rules. Use when planning UI, reviewing designs, or making design decisions. For implementation details, see styling-with-tailwind-shadcn.

• opensrc

  Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include

• organizing-fsd-architecture

  Guides organization of code using Feature-Sliced Design (FSD) architecture. Use when structuring projects, creating new features, determining file and layer placement, or reviewing architectural decisions. Also monitors codebase size and proactively suggests structural improvements.

• runtime-watch

  DorkOS runtime release watch, called from @dorkos-qa's heartbeat: compares the pinned Claude Agent SDK, Codex SDK and CLI, OpenCode SDK and Doe's Pi packages with npm, reads what changed, says whether it matters to DorkOS, and hands real drift to DorkOS Code for /app:runtime-upgrade. Reads and repor

• stewarding-ci-pipeline

  The method for changing the DorkOS CI pipeline as a measured experiment: the change protocol (hypothesis, ledger entry, census), PDCA, which constraint to work on first, the SLOs and ratchets, the fence around the steward and the judge, how to write a narrow hypothesis, and this repo's CI anti-patte

• syncing-agent-skills

  Keeps skill definitions aligned between Claude Code and Codex. Use when creating, migrating, renaming, or updating skills that must work across `.claude/skills` and `.agents/skills`, or when auditing drift between the two systems.

• verification-before-completion

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• vision-drift-check

  Weekly DorkOS scheduled skill: look for retired phrasing and stale positioning across the site, READMEs, docs, app copy and operating skills, check meta/ROADMAP.md against what shipped, and report what drifted from meta/VOICE.md. Reports only; never edits, commits or opens PRs.

• visual-companion

  Browser-based visual companion for showing mockups, diagrams, comparisons, and interactive options. Use when the user would understand something better by seeing it than reading it.

• writing-adrs

  Guides writing concise, effective Architecture Decision Records. Use when creating ADRs, extracting decisions from specs, or reviewing ADR quality.

• writing-app-copy

  The DorkOS in-app copy standard - voice, the word-count cap, and the rules for buttons, errors, empty states, confirmations, toasts, settings, approvals, status, times and truncation. Use when writing, editing or reviewing any string the DorkOS app renders (apps/client/src, or server copy the client

• writing-blog-posts

  Writes non-release DorkOS blog posts - feature posts, decision essays, ecosystem posts, and release recaps - from the repo's own ADRs, specs, research reports, and changelog fragments. Use when drafting, researching, or reviewing anything in blog/ that is not a version release note.

• writing-changelogs

  Writes human-friendly changelog entries and release notes. Use when populating changelog, preparing releases, or reviewing release notes quality.

• writing-developer-guides

  Structures developer guides for optimal AI agent and human consumption. Use when creating or updating files in contributing/, or when documentation needs to support autonomous coding agents.

• writing-for-humans

  Writes user-facing DorkOS prose a non-developer can read: changelog fragments, release notes, READMEs, npm copy, docs guides and concept pages, blog posts, UI microcopy, and error messages. Use when writing or reviewing any copy a person (not a coding agent) will read.

• writing-to-users

  Writes a direct reply to one person about their own report or question: GitHub issue replies, feedback receipt, decision and shipped emails, discussion answers, decline notes. Use when a named person is waiting to hear back from DorkOS in any channel. Builds on writing-for-humans; the standard it en

• adding-config-fields

  Patterns for adding, renaming, removing, or retyping fields in DorkOS user config. Use when editing UserConfigSchema, MarketplacesFileSchema, or any conf-backed store — walks the Zod field → defaults → conf migration → docs → test lifecycle end-to-end.

• clarifying-requirements

  Analyzes user prompts for gaps, ambiguities, and unstated assumptions, then asks clarifying questions before work begins. Use when requests are vague, lack acceptance criteria, or have hidden complexity.

• maintaining-dependencies

  Judgment for keeping a pnpm workspace's dependencies patched and current without a person in the loop — how to fix a transitive advisory, when an override is a lie, why cooldown does not apply to security patches, how to read a red Dependabot PR by its failure signature, and what a CodeQL alert need

• maintaining-dev-playground

  Keeps the Dev Playground current with the application. Use when editing UI components in apps/client/src/ — assesses playground candidacy, checks existing playground coverage, and guides adding or updating showcases. Also use when directly editing files in apps/client/src/dev/, building new widgets

• managing-specs

  Canonical rules for spec manifest management — statuses, transitions, and the manifest-ops script. Auto-loads when working with spec files.

• marketplace-dev

  Develop, validate, and publish DorkOS marketplace packages — agents, plugins, skill-packs, and adapters. Use when creating marketplace items, working in the dork-labs/marketplace repo, or helping users build packages for the personal marketplace.

• orchestrating-parallel-work

  Orchestrates parallel execution of AI agents with dependency analysis, batch scheduling, and the playbook for landing many branches at once. Use when coordinating multiple concurrent tasks, optimizing task ordering, sequencing batches of code changes into waves, landing parallel branches through rev

• reading-session-transcripts

  Resolves DorkOS session URLs to JSONL transcript files on disk and reads them. Use when the user shares a session URL, mentions "read this transcript", "read this chat", or references a DorkOS session they want analyzed.

• receiving-code-review

  Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

• requesting-code-review

  Guides dispatching a code-reviewer subagent to verify work before proceeding. Use when completing tasks, implementing major features, or before merging to verify work meets requirements.

• styling-with-tailwind-shadcn

  Implements the Calm Tech design system using Tailwind CSS v4 and Shadcn UI. Use when writing styles, building components, or theming. For design decisions, see designing-frontend.

• test-driven-development

  Use when implementing any feature or bugfix, before writing implementation code

• upgrading-runtime-dependencies

  Guides strategic analysis of agent runtime dependency upgrades — changelog categorization, codebase impact assessment, and feature adoption decisions. Use when upgrading SDK-level dependencies that sit behind an abstraction boundary.

• working-in-worktrees

  Decides when agent work needs an isolated git worktree and how to create, enter, and clean one up safely. Use when starting code changes in a checkout that may be shared with another agent, dispatching a Linear task, executing a spec, or running any parallel work that mutates tracked files.

• dorkbot-triage

  Labeling helper for incoming GitHub issues on dork-labs/dorkos. Use when DorkBot is asked to label the issue queue: set a type and runtime label on each new issue and flag likely duplicates. Read-and-suggest by default; only edits labels when explicitly allowed to act. Replies to reporters belong to

• tidy-notes

  Use when the person asks to tidy their notes with the Agent Tools Fixture.