timothyvang
- 18 skills
- 0 followers
- yesterday last updated
- ▌ Project Brief · timothyvang bundleMaintainer workflow that opens a repo to many contributors and their agents: writes docs/PROJECT_BRIEF.md, proposes claimable GitHub Issues, installs the overlap and roadmap scripts your agent runs, PR and issue templates, and CONTRIBUTING.md, so anyone can run /deepmodebot:contribute. Re-run to refresh the brief and roadmap, post overlap comments, and release expired claims. Use for /skill:project-brief, "publish this project for contributors", or "set up the task board".
- ▌ Agent Harnesses · timothyvang bundleCited, dated facts for omp, Claude Code, Codex and Antigravity SDKs; harness installation, embedding, configuration, hooks, permissions and delegation; MCP, ACP, A2A and WebMCP; LangChain, LangGraph, Deep Agents and LangSmith. Use for SDK or framework selection, agent applications, middleware routing, checkpoint/replay, memory, evals, deployment and bounded loops.
- ▌ Cloud Devsecops · timothyvang bundleDocker, Compose, container images and runtimes, Kubernetes operations and ecosystem tooling; security and DevSecOps rules for AWS, Azure and Google Cloud, IAM, policy, pipelines, supply chain and IaC. Use when building or debugging containers, operating workloads, choosing container tools, or changing cloud access and deployment infrastructure.
- ▌ Secrets And Auth · timothyvang bundleRules and free-first tool picks for secrets and agent authentication: .env and secret sharing, password managers, logins and MFA for agents, OAuth delegation, MCP server auth, CI OIDC, secret scanning, and leak response. Use when a task touches secrets, credentials, tokens, logins, or auth.
- ▌ Software Architecture · timothyvang bundleCited guidance on repo layout and monorepo tooling, domain vocabulary and typed models, knowledge graphs, choosing and migrating databases, multi-tenancy, queues and durable workflows, API style, reliability, observability, deployment, and IaC. Use when designing or changing structure, data models, databases, or backend infrastructure.
- ▌ Create Verification Skill · timothyvang bundleGenerate a project-local verification skill (.omp/skills/verify-<app>/) that drives the app the way a user does and captures proof: control CLI, launch/doctor/drive/evidence/cleanup, and a feature map. Any language or platform. Use for /skill:create-verification-skill, "make a verify skill for this repo", or when a repo has no scripted way to prove UI/CLI/service behavior.
- ▌ Maintain Verification Skill · timothyvang bundlePeriodic pass that keeps a project's verify-<app> skill and feature map honest: parallel read-only source readers per feature, one live session driving every feature, at most one change set of proven corrections. Use for /skill:maintain-verification-skill or "audit the verify skill".
- ▌ Frontend UI · timothyvang bundleUI and UX rules for building, restyling, or reviewing interfaces: components, layout, typography, color, motion and animation, motion graphics, accessibility, copy, and chat or agent UI, with patterns learned from shipped apps. Use before writing or reviewing UI code.
- ▌ Domain Rules · timothyvang bundleEngineering rules by domain: AI agents and LLMs, AWS networking, backend system design, language ecosystems and their traps, DevOps and computer-science fundamentals, and engineering practice (debugging, legacy code, incidents, estimates). Use when designing or reviewing work in one of those areas.
- ▌ Deep Stack · timothyvang bundleStack picks and ship loop: a 2026 default software stack and the decision rules behind it, applied to any app (web, CLI, desktop, mobile, AI agent, data/ML, security tooling), plus an agent-driven UI design workflow and a per-task ship loop (worktree, service-layer build, recorded evidence, reviewed PR). Use when the user asks to pick a stack, "what stack", or to build a tech stack for a new app; designs a UI with an agent via a design system; or wants one change shipped as an evidence-backed, reviewed PR. An issue queue run as a software factory is deepmodebot's Work a queue playbook, factory source.
- ▌ Deepmodebot · timothyvang bundleEngineering rigor for /deep, Deepmodebot, or rigor requests on large/risky work: restate, choose a playbook, apply named principles, prove real behavior, report evidence.
- ▌ Verify Deepmodebot · timothyvang bundleVerifies deepmodebot's real agent delivery, sealed review and workflow evaluation CLIs, records evidence, and distinguishes runtime proof from structural tests. Use before changing or verifying these surfaces.
- ▌ Contribute · timothyvangJoin someone else's project as a contributor: learn it from the maintainer's brief, pick an unclaimed `help wanted` issue that doesn't overlap open PRs or claims, claim it, build and prove it the deepmodebot way, and open a PR. Use for /deepmodebot:contribute, "help out on this repo", or "find me something to work on".
- ▌ Grill With Docs · timothyvang bundleGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- ▌ Qc · timothyvang bundleQuick commit + auto-push. Stages changes, drafts a Conventional Commit message from the diff, commits, and pushes. `/qc` pushes the current branch to its origin upstream; `/qc main` switches to main first and pushes there (solo-speed flow — skips PR review). Bootstraps `gh` (install + browser auth) if not already configured. Never bypasses hooks (`--no-verify`), signing (`--no-gpg-sign`), or rewrites commits (`--amend`). No AI attribution lines in commit messages.
- ▌ Diagnose · timothyvang bundleDisciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
- ▌ Github Triage · timothyvang bundleTriage GitHub issues through a label-based state machine. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
- ▌ Improve Codebase Architecture · timothyvang bundleFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.