All authors
Claude Skills by Vinix24
github.com/Vinix2449 skills0 installs55 views
- OrchestrateThis is the extended reference for the headless T0 orchestrator. The condensed identity is in `agents/orchestrator/CLAUDE.md`.Votes: 0GitHub stars: 61
- Api DeveloperAPI developer specializing in clean, well-documented REST APIsVotes: 0GitHub stars: 61
- ArchitectSystem architecture specialist for designing robust, scalable solutionsVotes: 0GitHub stars: 61
- Backend DeveloperBackend developer creating fault-tolerant, scalable server-side solutionsVotes: 0GitHub stars: 61
- Data AnalystSEO data analysis, pattern identification, and actionable insights generationVotes: 0GitHub stars: 61
- Database EngineerSQLite database expertise for migrations, multi-tenant patterns, transactional safety, FTS5 virtual tables, and schema evolution. Use this skill for ANY work involving schema changes, data migrations, INSERT/UPSERT semantics, FTS5 rebuilds, transaction rollback design, multi-tenant data isolation, or SQLite performance tuning. Triggers include: writing migration SQL, modifying `_import_table`-style importers, designing UNIQUE/PK constraints, adding indexes for JOINs, debugging "rows missing" ...Votes: 0GitHub stars: 61
- DebuggerSystematic debugging specialist focused on root cause analysisVotes: 0GitHub stars: 61
- Excel ReporterComprehensive formatted Excel report generation with Dutch market compatibilityVotes: 0GitHub stars: 61
- Frontend DeveloperFrontend specialist creating distinctive, production-grade interfacesVotes: 0GitHub stars: 61
- Intelligence EngineerVNX-specific domain expertise for the intelligence system, central state databases, and dispatch lifecycle. Use when working on quality_intelligence.db / runtime_coordination.db / dispatch_tracker.db, code_snippets FTS5, snippet_metadata linkage, success_patterns / antipatterns, T0 state projection (t0_state.json), intelligence_injections lifecycle, dispatch → receipt → events → archive flow, central state architecture, project_id propagation across VNX, or any code that reads/writes VNX gove...Votes: 0GitHub stars: 61
- Monitoring SpecialistSystem monitoring, alerting, and observability implementationVotes: 0GitHub stars: 61
- Performance ProfilerSystem bottleneck identification, resource optimization, and performance analysisVotes: 0GitHub stars: 61
- PlannerPlanning specialist for PR-based feature breakdown and FEATURE_PLAN.md generationVotes: 0GitHub stars: 61
- Python OptimizerPython code performance optimization specialistVotes: 0GitHub stars: 61
- Quality EngineerComprehensive quality validation specialist ensuring production readiness through evidence-based testing.Votes: 0GitHub stars: 61
- ReviewerSenior engineer conducting thorough, constructive code reviewsVotes: 0GitHub stars: 61
- Security EngineerSEOcrawler security vulnerability scanner and hardening specialist for comprehensive security audits.Votes: 0GitHub stars: 61
- Supabase ExpertSupabase database optimization specialistVotes: 0GitHub stars: 61
- T0 OrchestratorMaster orchestration for the VNX multi-terminal system. Governs receipt review, quality/risk interpretation, open-items lifecycle, PR completion decisions, and single-block dispatch creation across T1/T2/T3.Votes: 0GitHub stars: 61
- Test EngineerTest engineer ensuring quality through comprehensive testing strategiesVotes: 0GitHub stars: 61
- Vnx ManagerVNX orchestration infrastructure guardian - maintains dispatcher, smart tap, receipt processor, intelligence systems, and documentation.Votes: 0GitHub stars: 61
- Api DeveloperAPI developer specializing in clean, well-documented REST APIsVotes: 0GitHub stars: 61
- ArchitectSystem architecture specialist for designing scalable solutions that handle complexity and evolve under changeVotes: 0GitHub stars: 61
- Backend DeveloperBackend developer creating fault-tolerant, scalable server-side solutionsVotes: 0GitHub stars: 61
- Control CentreMulti-project Control Centre supervisor. Supervisors N per-project T0's from a single interactive Claude Code session. Read-only orchestration — no code writes.Votes: 0GitHub stars: 61
- Data AnalystSEO data analysis, pattern identification, and actionable insights generationVotes: 0GitHub stars: 61
- Database EngineerSQLite database expertise for migrations, multi-tenant patterns, transactional safety, FTS5 virtual tables, and schema evolution. Use this skill for ANY work involving schema changes, data migrations, INSERT/UPSERT semantics, FTS5 rebuilds, transaction rollback design, multi-tenant data isolation, or SQLite performance tuning. Triggers include: writing migration SQL, modifying `_import_table`-style importers, designing UNIQUE/PK constraints, adding indexes for JOINs, debugging "rows missing" ...Votes: 0GitHub stars: 61
- DebuggerSystematic debugging specialist focused on root cause analysisVotes: 0GitHub stars: 61
- Excel ReporterFull-coverage formatted Excel report generation with Dutch market compatibilityVotes: 0GitHub stars: 61
- Fabric ReferenceRead-only runbook for how the VNX fabric actually works — state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric operation instead of rediscovering it, or when a fabric command behaves unexpectedly. Companion to the t0-orchestrator skill (judgment) and vnx-manager (infra maintenance); this...Votes: 0GitHub stars: 61
- Featureplan KickoffVNX feature-execution kickoff preflight. USE THIS when starting or resuming a feature or track from its plan: checking worktree/queue/staging health, finding the first promoteable dispatch, and handing off to @t0-orchestrator. Reads the feature's track + plan doc from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md/PR_QUEUE.md are generic examples, not the source.Votes: 0GitHub stars: 61
- Frontend DeveloperFrontend specialist creating distinctive, production-grade interfacesVotes: 0GitHub stars: 61
- HorizonStrategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is ...Votes: 0GitHub stars: 61
- Intelligence EngineerVNX-specific domain expertise for the intelligence system, central state databases, and dispatch lifecycle. Use when working on quality_intelligence.db / runtime_coordination.db / dispatch_tracker.db, code_snippets FTS5, snippet_metadata linkage, success_patterns / antipatterns, T0 state projection (t0_state.json), intelligence_injections lifecycle, dispatch → receipt → events → archive flow, central state architecture, project_id propagation across VNX, or any code that reads/writes VNX gove...Votes: 0GitHub stars: 61
- Monitoring SpecialistSystem monitoring, alerting, and observability implementationVotes: 0GitHub stars: 61
- PanelMulti-provider deliberation panel for COMPLEX, multi-view questions — architecture, strategy, market research, and codebase sweeps. Runs a 4-stage deliberation across the provider fleet (diverge → contrarian red-team → adversarial verify → cited synthesis), the same multi-perspective rigour the plan-gate already applies to plan reviews, generalised to arbitrary questions. Use when one model's answer isn't enough and you want convergence THROUGH disagreement + verification, not a single opinion.Votes: 0GitHub stars: 61
- Performance ProfilerSystem bottleneck identification, resource optimization, and performance analysisVotes: 0GitHub stars: 61
- PlannerPlanning specialist that breaks a VNX feature or track into small, independently-shippable PRs with dependencies and per-PR task-class routing. USE THIS when the user wants to break a feature down into PRs, sequence the work, or turn a plan into a PR queue. Delegated to by @horizon (formerly @pm — @pm still resolves via alias). Works from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md is a generated generic example, not the source.Votes: 0GitHub stars: 61
- PmBackward-compat alias for @horizon (this skill was renamed from `pm` to `Horizon` on 2026-07-05). USE THIS only when invoked directly as `/pm` or via an existing `@pm` delegation reference — it redirects immediately to @horizon, the strategic owner of the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. Prefer `@horizon` / `vnx horizon` for anything new; this alias exists only for transition safety.Votes: 0GitHub stars: 61
- Python OptimizerPython code performance optimization specialistVotes: 0GitHub stars: 61
- Quality EngineerQuality validation specialist covering functional, performance, and security testing to ensure production readiness through evidence-based testing.Votes: 0GitHub stars: 61
- ReviewerSenior engineer conducting thorough, constructive code reviews. Round-2+ reviews use adversarial framing to find missed cases and convergent failure modes.Votes: 0GitHub stars: 61
- Security EngineerSEOcrawler security vulnerability scanner and hardening specialist covering code analysis, dependency audits, and infrastructure review.Votes: 0GitHub stars: 61
- Supabase ExpertSupabase database optimization specialistVotes: 0GitHub stars: 61
- T0 OrchestratorMaster orchestration for the VNX multi-terminal system. Governs receipt review, quality/risk interpretation, open-items lifecycle, PR completion decisions, and single-block dispatch creation across T1/T2/T3.Votes: 0GitHub stars: 61
- Test EngineerTest engineer ensuring quality through unit, integration, and E2E testing strategiesVotes: 0GitHub stars: 61
- Vnx ManagerVNX orchestration infrastructure guardian - maintains dispatcher, smart tap, receipt processor, intelligence systems, and documentation.Votes: 0GitHub stars: 61
- Fabric ReferenceRead-only runbook for how the VNX fabric actually works — state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric operation instead of rediscovering it, or when a fabric command behaves unexpectedly. Companion to the t0-orchestrator skill (judgment) and vnx-manager (infra maintenance); this...Votes: 0GitHub stars: 61
- HorizonStrategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is ...Votes: 0GitHub stars: 61