AI Agent Workflow Collection

Privacy-first analytics — event taxonomy, funnel design, user insights. Use when adding analytics, defining events/metrics, designing funnels, or interpreting user behavior.

Backend architecture — API design, database schema, authentication. Use when designing or reviewing a backend, REST/GraphQL APIs, data models, or auth flows.

Ideal-vs-current gap analysis — research 5-10 comparable projects, synthesize the ideal architecture, produce a dimension-by-dimension gap table. Use when benchmarking against best-in-class or deciding which architectural gaps to close.

Project health system — profile-based assessment, transformation, and progress tracking. Use when assessing overall project health, planning a transformation, or tracking improvement over time.

Data-backed brief — research, source, double-verify, and render a visually rich single-file HTML report. Use when the user wants a sourced, fact-checked brief or report on a topic.

Smart commits — quality gates, atomic grouping, Conventional Commits formatting. Use when committing changes, grouping a working tree into atomic commits, or writing commit messages.

Security and regulatory compliance — OWASP, privacy laws, data protection, web security, i18n. Use when auditing for security/privacy compliance, GDPR/KVKK, or pre-release legal review.

CV generator — professional, ATS-compatible HTML CV plus a LinkedIn companion guide. Use when creating or updating a resume/CV or optimizing a LinkedIn profile.

Deployment and infrastructure — containerization, deployment, monitoring, incident response. Use when deploying an app, setting up containers/monitoring, or planning incident response.

Dependency upgrade loop — classify each dependency as safe-patch/safe-minor/review-major, apply safe groups with per-group commits, surface majors with migration notes and rollback. Use when upgrading dependencies or auditing for outdated/vulnerable packages.

DevOps audit — CI/CD pipelines, code signing, dependency management, deployment config for any stack. Use when auditing or setting up CI/CD and release infrastructure.

Documentation gap analysis — identify missing docs and generate what is needed. Use when documentation is incomplete, or the user asks to write/improve README, API docs, or guides.

Universal code quality fix — format, lint, type-check, l10n, and security scan for any stack. Use when the user asks to fix code quality, run formatters/linters/type-checks, or scan for secrets.

Release scope triage — collaboratively decide which features ship this release vs defer to backlog, file/implement the kept set, sync docs to match. Use when a release has grown too complex to finish or polish everything, and the team needs to cut scope deliberately instead of drifting.

Frontend design quality — design-system audit, token enforcement, component states, accessibility, responsive layout, theming. Use when building or reviewing UI for design consistency, a11y, or responsiveness.

Project scaffolding — generate production-ready project structure for any stack. Use when starting a new project or bootstrapping a repo skeleton.

GitHub-Issues lifecycle in one skill — file a verified deduped issue, sweep the set for duplicates, audit done-ness from code, and execute an issue end-to-end (re-verify → impact map → implement → code-proven close). Use to open, refine, sweep, status-check, or do an issue.

Store and release management — store submission, listing optimization, release strategy, post-launch monitoring. Use when preparing an app-store release or planning a launch.

Marketing and growth — positioning, copy generation, and growth tactics for indie and solo-dev products. Use when crafting positioning, marketing copy, or a growth plan.

Mobile app quality audit — 145+ rules across 13 domains with release-readiness scoring (Flutter, SwiftUI, Kotlin/Compose, React Native). Use when auditing a mobile app for quality or release readiness.

Spec pipeline conductor — run the Spec Kit chain (specify→clarify→plan→tasks→analyze) with blocking gates, enforce a verify-criteria task contract, and hand off a commit-ready plan. Use when turning a feature idea into an executable, test-gated plan.

Smart pull requests — Conventional Commit title and clean body for release-please. Use when opening or formatting a pull request.

Paid-product readiness — monetization model, billing/entitlement integrity, pricing/packaging, go-to-market baseline. Use when turning a project into a paid product or auditing an existing monetization setup.

Quality-by-Mechanism — installs a deterministic, local, no-CI quality gate (format → lint → type → test) enforced via a host-appropriate mechanism (Claude Code Stop hook, Aider auto-lint/test, or git pre-commit). Use when the user asks to enforce quality, set up a quality gate, or block "done" until checks pass, without relying on CI.