Recently added

Build, inspect, and debug UI components using @barefootjs/cli (>= 0.11.0). Covers component discovery, scaffolding, signal inspection, reactive performance profiling, and previews.

Task-specific expert council and real-world decision support that preserves named human authority.

Task and activity orchestration for AI coding agents. Adds Orbit's MCP task and knowledge surface plus workflow skills to Codex.

An engineering workflow for Claude Code. One idea goes in; a reviewed, integrated commit comes out.

Synthesize project, calendar, CRM, and Cortex context into concise weekly client-status drafts for user review.

Find recent stories, rank them for a configured audience, and assemble a voice-matched roundup with traceable sources.

Create an engagement plan, portable AI workspace prompt, folder blueprint, next action, and optional Cortex nodes from approved inputs.

Review relationship context, cooling periods, and positive moments to prioritize referral actions and draft voice-matched asks.

Turn calendar events into a local, reviewable time log and generate invoice drafts from configured client billing rules.

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

Run real-browser end-to-end (E2E) acceptance tests on your web app from any AI coding agent. Generate test scripts from plain English, replay them on localhost, capture screenshots, and validate user flows like signup, checkout, and dashboards. Works across Claude Code, Cursor, Codex, and Windsurf.

開發流程慣例，除發版流程（.NET / NuGet 專屬）外與程式語言 / 框架無關：計畫文件（預設 docs/plans/，可依 repo 約定改放 gitignored 目錄）的撰寫與格式、定案後交接給接手的 session（不限程式碼實作，交接文件也不限是 plan）、實作期間的驗證閘門（plan 版本確認、範圍對帳、平行路徑檢查）、Claude Code 設定檔語料的定期健檢（含 plugin 版本漂移與自有 marketplace 的清單一致性）。CHANGELOG 草稿整理（依既有慣例偵測後沿用）。.NET / NuGet 的發版流程（前置檢查、版號判定、出貨基準合併 —— PublicAPI 與 analyzer release tracking 兩份、分兩次推送）。後續擴及 CI 與源碼掃描。

Replaces the spinner with an animated ASCII slot machine: pull the lever on every prompt, watch the reels spin while Claude works, cash in when the turn completes.

Org-mode task tracking for Claude Code: org_* MCP tools via a Doom Emacs module, a queued state/clock event architecture reviewed by a human, session-tracking hooks, and the org skill with its conventions as references.

Command-free, skills + subagents plugin for fast single-feature development: digest a plan, get approval, isolate in a worktree, implement, and open a PR — Sonnet build / Opus review, with graded effort.

Higher Agents for Codex: rigorously plan, implement, review, and merge one feature with controlled subagents and fail-closed gates.

Ask a fresh Claude session to review branch and local changes, implement a milestone plan test-first in an isolated worktree, and provide the bounded internal second opinion used by ca dual review.

Claude Code Higher Agents for building ONE feature thoroughly: deep red-teamed plan to human approval, per-task implementation review, a risk-scaled pre-PR gate, independent PR review, rigorous feedback handling, gated merge, conflict resolution, and safe worktree cleanup. Requires the superpowers plugin; model-agnostic.

Ask a fresh Claude session to review branch and local changes, implement a milestone plan test-first in an isolated worktree, and provide the bounded internal second opinion used by ca dual review.

Ask a fresh Codex session to review branch and local changes, or run the ca feature loop: plan with Codex, review milestone and final PRs, synthesize findings, and provide gated merge, conflict resolution, and safe worktree cleanup.

Capture and enrich innovations from conversations or technical sources, request patent preparation, and respond to Lightbringer report and patent-draft reviews.

Carries a pull request from opened to landed: draft state that tracks convergence, same-cycle review-comment triage, line accounting against the stated purpose, and a human hand on the merge by default (an owner-applied merge-when-green label is the standing approval).

Repository documentation that skims well and names real code: the device picked from the content, a paragraph-cap and path probe, fact-preserving restructures, and the architecture page whose boxes name real symbols.

Keeps the Codex desktop Chrome plugin driving Brave and other Chromium browsers: cache sync after app updates, browser-only auth under a custom model provider, and browser-family selection.

Use Wannalead's LinkedIn workflows through its hosted MCP server.

Route every Claude Code tool call through a nucleus Firecracker microVM under an information-flow permission lattice, with a signed mediation receipt per call.

Контроль качества разработки 1С:Предприятие (BSL): стандарты #stdNNN, принципы структурного и объектно-ориентированного программирования, паттерны проектирования применительно к 1С, корректность XML-структур метаданных. Блокирующие гейты не дают объявить работу законченной, пока проверки не прогнаны, а машиночитаемый след фиксирует, что именно проверено и что пропущено.

Token-efficient WB CLI operations and safe multi-repository workflows

Generic GitHub workflow commands for issue management, PR creation, code review, and releases. Works with any repository by auto-detecting settings.

Skill-driven workflow plugin for GitHub development with excellence-by-default quality gates. Encodes team knowledge as composable skills, enforces safety through hooks, and compounds learning across sessions. Strict TDD, Stranger Test, holdout validation, and evidence-based verification built in. Durable goals, workflows, triggers, and runs at .flow/. Requires bash, git, gh, jq, and python3 with PyYAML; on Windows, Git Bash (see docs/windows-support.md).

Evidence-first project documentation system. Produces an audit-ready 23-file package for technical due diligence, engineering and product onboarding, and partner or customer communication — every material claim traced to a ledger row and a claim state, three context-isolated verification passes, and a binary release gate. Ships a post-merge GitHub Actions job that keeps the package current by opening a documentation PR. Requires bash, git and jq; on Windows, Git Bash (see docs/windows-support.md).

NCI (Narrative Credibility Index) manipulation detection with integrated deep research fact-checking. Analyzes content for propaganda, disinformation, and manipulation patterns across 20 categories. Includes claim verification using deep research methodology.

Structured product development methodology with traceable evidence, explicit decisions, and constrained spec generation. Forces auditability through semantic IDs, quality gates, and impact-aware updates.

Fourteen opinionated skills that guide founders and leaders through designing, deploying, adopting, and evolving organizations where agents handle coordination and execution while humans own specification and judgment. Diagnose coordination overhead, encode organizational identity, write agent-ready specifications, convert approvals into quality gates, validate gates against hidden holdout scenarios, architect governance ecosystems, redesign roles around value flows, navigate political dynamics, operationalize designs into agent-consumable primers, run post-deployment evolution audits, generate role-specific agent configurations, build per-role AI maturity matrices, design structured adoption sprints, and write human-facing AI usage policies with risk model reasoning.

Agentic Delivery Lifecycle: interview-driven repo intake, app classification, hardened Dockerfiles, Terraform on Azure, GitHub Actions CI/CD with immutable tags, deployment verification and Jira tracking. Every platform choice is an interview option.

WordPress / CMS engineering team — agents (wordpress-architect, wordpress-developer, wordpress-ops-engineer) for building, extending, and operating WordPress done right: the build-approach decision (classic vs block/FSE theme, plugin vs theme vs must-use, headless/decoupled vs traditional, single vs multisite), secure block & theme & plugin development (block.json, hooks/filters, WP_Query, the REST API, sanitize-in/escape-out, $wpdb->prepare, nonce + capability checks), and operations (page + object cache/Redis, security hardening, safe updates with staging & backups, migrations). skills, a decision-tree knowledge bank (Mermaid trees + a dated 2026 stack map), best-practices, templates, commands, an advisory hook. Seams: decoupled front-end -> frontend-engineering, non-WP backend/APIs -> backend-engineering, infra perf budget -> performance-engineering, formal security verdict -> security-engineering. Requires ravenclaude-core@>=0.7.0.

Web-scraping & data-extraction engineering team — agents (extraction-architect, scraper-implementation-engineer) answering 'how do we acquire this web data legally, robustly, and at the right cost?': API-vs-scrape source choice, a legal/ethical gate (robots.txt, ToS, public-vs-authenticated, rate, PII/copyright) BEFORE any code, fetch strategy (HTTP vs headless, JSON-endpoint-first), resilient parsing (structured data over brittle selectors, validate-to-schema), change-detection & re-crawl scheduling, and the extract→validate→dedup→store pipeline with provenance. skills, a knowledge bank (a Mermaid decision tree + a dated 2026 tooling/legal reference). Distinct from data-orchestration/data-streaming (move data that ALREADY exists) and backend-engineering — this team owns ACQUIRING web data. Legality-first: anti-bot is a stop-signal, never evasion for abuse; ToS/robots specifics volatile + jurisdictional, retrieval-dated + verify-at-use. Needs ravenclaude-core.

Web design & build specialist team — web architect (IA, stack, hosting), UX designer (wireframes, flows, conversion), visual designer (brand, typography, tokens), frontend implementer (HTML/CSS/JS, React, Astro, Next), content strategist (copy, microcopy, SEO content), accessibility auditor (WCAG 2.2 AA/AAA), performance engineer (Core Web Vitals, image/font optimization). skills (the gold-standard-website-pipeline build pipeline + static-site build, design-system audit, brand-guidance authoring (anti-pattern catalogue), card/tile UI, accessibility review, Core Web Vitals tuning, technical SEO audit, information architecture, conversion design, content audit, design-tokens scaffolding, third-party hygiene, Fluent UI v9 + React implementation), templates, commands, an advisory hook, and a knowledge bank seeded with a curated 2026 reference set of "cutting edge yet simple" marketing-site donors — the design agents carry compact inline priors plus a pointer to the full brief. Inherits ravenclaude-core protocols.

Web commerce integration specialist — scaffolds production-ready payment/commerce backends (Stripe, Square, or Shopify; one per site) into static or JS-framework sites at full depth: catalog, cart, hosted/embedded checkout, verified webhooks, idempotency, POS/inventory reconciliation, and order handling. Three first-class provider tracks behind a thin shared payment-lifecycle contract — NOT a leaky unified adapter. Generates first-party code (no dormant/deprecated deps), with PCI card-isolation, webhook signature verification, idempotency, and env-only secrets as GENERATED-CODE invariants. The backend-integration lane that plugs into web-design's build pipeline; every payment/PII security verdict routes to ravenclaude-core/security-reviewer. Inherits ravenclaude-core protocols.

Wealth Management (RIA Practice) specialist team — agents (ria-practice-lead, aum-revenue-analyst, client-segmentation-specialist, compliance-cadence-specialist), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. A practice-ops team for an RIA principal, COO, or ops lead accountable for organic growth and advisor capacity — it separates net-new flows from market appreciation, segments clients by profitability, sizes capacity by households, and treats the compliance cadence as non-negotiable. NOT investment advice; fiduciary/SEC determinations route to compliance counsel. Inherits ravenclaude-core protocols.

Waste & recycling operations team — agents (waste-operations-lead, route-and-diversion-specialist) answering 'how do we collect, haul, dispose of, and divert waste PROFITABLY, SAFELY, and in COMPLIANCE?': collection streams (MSW, recycling, organics, C&D; residential/commercial/roll-off), fleet (front/rear/side-load ASL, roll-off, RNG/EV), transfer stations & Subtitle D landfill (tipping fees, airspace), RCRA Subtitle D compliance, DOT/CDL safety — plus route optimization (density is the profit driver; static vs dynamic; RouteWare/Routeware-AMCS/Trux), diversion measurement, MRF & commodity economics (OCC/PET/HDPE/aluminum/mixed paper; contamination is the killer; post-National-Sword prices), and mandates (EPR, SB 1383, landfill bans). skills, a knowledge bank, templates. Distinct from esg-sustainability-reporting (corporate disclosure), fleet-logistics (generic telematics/DOT), and hazardous-waste RCRA Subtitle C response (out of scope). Requires ravenclaude-core@>=0.7.0.

Veterinary Practice specialist team — agents (vet-practice-lead, clinical-protocol-specialist, practice-operations-manager, vet-finance-analyst), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. A clinical-and-practice-management team for a veterinary hospital owner or medical director — it builds standardized care protocols, runs the practice on production and ACT (average client transaction), manages the appointment-and-doctor capacity that gates revenue, and frames the independent-vs-corporate position in a fast-consolidating market. Inherits ravenclaude-core protocols.

UX-research team — agents (ux-research-lead, research-execution-and-synthesis-specialist) that turn a fuzzy ask into a researchable question, pick a rigorous method (generative vs evaluative, qual vs quant, moderated vs unmoderated), run the study (usability tests, interviews, surveys), and synthesize evidence into decision-ready, bias-checked insight — without the research theater. The lead owns framing, method selection, the research plan, research-ops (recruiting, repository), and research ethics + participant-PII discipline (consent, anonymization). The specialist owns protocol & task design, non-leading moderation, survey design, and synthesis (affinity/thematic analysis, evidence strength, observation vs interpretation). skills, a knowledge bank + templates. Distinct from product-management (roadmap/prioritization), web-design (visual/interaction/IA design), experimentation-growth-engineering (online A/B stats), data-science-research (advanced quant). Requires ravenclaude-core@>=0.7.0.

Trust & Safety team — agents for content-moderation and abuse-detection work. The trust-safety-policy-lead designs the policy taxonomy + enforcement ladder, the human-review operations layer (queue prioritization, reviewer wellness, escalation, appeals/due-process), and the measurement frame (prevalence, enforcement precision/recall, time-to-action SLA, appeal-overturn rate). The abuse-detection-engineer builds the detection stack: signals, rules-vs-ML classifiers, reviewer queues, thresholds tied to precision/recall. skills, a knowledge bank (a Mermaid enforcement decision tree + a T&S metrics catalogue with formulas), templates, best-practice rules, and an advisory hook. Seams: classifier-eval validity → applied-statistics; PII → data-governance-privacy; account-takeover → security-engineering; LLM-classifier build → claude-app-engineering. Enforcement is proportional; appeals are due process; measure prevalence, not just volume. Requires ravenclaude-core@>=0.7.0.

Corporate treasury team — agents (treasury-strategy-lead, cash-and-risk-operations-specialist) answering 'how much cash, where — who banks us, and how do we protect the money?': cash & liquidity forecasts (CCC, direct/indirect, 13-week), liquidity-buffer & facility policy, bank-relationship & account structure (ZBA, notional/physical pooling, in-house bank, AFP fees, BAI/ISO 20022), investment policy (IPS) & debt covenants, FX & rate hedging (transaction/translation/economic exposure, forwards/swaps/options/collars, ASC 815 / IFRS 9 hedge accounting), payments & fraud controls (positive pay, dual auth, BEC), working-capital & TMS selection. skills, a knowledge bank, and templates. Distinct from finance (FP&A/budgeting), fintech-payments-engineering (rail code), and regulatory-compliance (AML/OFAC) — treasury owns the CASH and the BANK RELATIONSHIP. Not legal/tax/accounting advice; volatile hedge-accounting & bank/regulatory specifics carry a retrieval date + verify-at-use. Needs ravenclaude-core.