All authors
Claude Skills by djnsty23
github.com/djnsty2366 skills0 installs119 views
- A11yAccessibility audit against WCAG 2.1 AA — run the automated scan, then the manual checks tooling cannot make, and report in this project's format.Votes: 0GitHub stars: 6
- Archive PrdArchives completed stories from prd.json to reduce token usage.Votes: 0GitHub stars: 6
- AuditParallel quality audit across specialized agents. Finds bugs, violations, and quality issues. Use audit for fixes, brainstorm for features.Votes: 0GitHub stars: 6
- AutoAutonomous task execution with testing and security. Works through all tasks without stopping.Votes: 0GitHub stars: 6
- BrainstormFeature ideation, dead code cleanup, and product thinking. Proposes new features and architecture improvements — not bugs or violations (use audit for those).Votes: 0GitHub stars: 6
- CommitCommit, push and open a pull request to this repo standard: a conventional subject, a body saying why the change is needed, the message passed by file rather than inline, no co-author trailer, explicit paths staged rather than everything, and the gate run before the push.Votes: 0GitHub stars: 6
- CoreThe prd.json schema and task system used by every autodev workflow. Load before reading or writing prd.json, creating stories, or interpreting a task's passes field.Votes: 0GitHub stars: 6
- DesignCreates distinctive UI with preserved structure. Avoids generic AI aesthetics. Use when designing or refining user interfaces.Votes: 0GitHub stars: 6
- PerfWeb performance audit against this project's Core Web Vitals and bundle budgets, with a fixed report format.Votes: 0GitHub stars: 6
- RemotionBest practices for Remotion - video creation in React. Use when working with video compositions, animations, or subtitles.Votes: 0GitHub stars: 6
- ReviewReview changed code for correctness and quality, then apply the project-specific checks Claude Code's built-in reviewer does not know about.Votes: 0GitHub stars: 6
- SecurityFind the security defect in code before it ships: secrets in source or in schema files, Supabase RLS and access policies, session and sign-out scope, a user id read from the payload or a header instead of the verified session, and unvalidated external input.Votes: 0GitHub stars: 6
- SeoSEO audit and structured data patterns - meta tags, Open Graph, JSON-LD schema, Core Web Vitals. Use for marketing sites and e-commerce.Votes: 0GitHub stars: 6
- Setup ProjectScaffolds new projects or onboards existing ones. Detects stack, creates monorepo/single-app, configures strict tooling. Use for greenfield or first-time setup.Votes: 0GitHub stars: 6
- ShipPre-deploy checklist with review, security, and test verification. Use when ready to deploy.Votes: 0GitHub stars: 6
- SprintCreates or advances sprints in prd.json. Use when starting new work cycles or closing completed sprints.Votes: 0GitHub stars: 6
- StandardsThe conventions this project holds code to — UI state completeness, design tokens, type-safety boundaries, query-key shape, and the anti-patterns to flag on sight.Votes: 0GitHub stars: 6
- StatusShows sprint progress and task status. Use 'progress' (not 'status' - that's a built-in).Votes: 0GitHub stars: 6
- StripeStripe integration patterns - API keys, webhooks, checkout, subscriptions. Loads when working with payments.Votes: 0GitHub stars: 6
- SupabaseSupabase CLI, Postgres performance, and schema patterns. Use for database operations, queries, RLS, and migrations.Votes: 0GitHub stars: 6
- TestRuns unit and browser tests on latest changes. Use after implementing features or fixing bugs.Votes: 0GitHub stars: 6
- Adversarial LoopRun an independent-context tests-first review loop: an adversary model authors failing acceptance tests, the building agent fixes against them, and bounded review rounds end on an exact verdict token. Use for changes where a wrong fix is expensive — gates, harnesses, security paths, anything that grades other code.Votes: 0GitHub stars: 6
- References`[measured 2026-08-25]` Historical decision and reported outcome counts follow. They are retained as evidence of that decision, not a current causal comparison or permission to skip verification. Revisit using new observations, not architecture preference.Votes: 0GitHub stars: 6
- Auto BrainRun Brain's assigned mission while the user is away. Use when asked to coordinate the fleet autonomously, carrying work through implementation, verification and the authorized release boundary.Votes: 0GitHub stars: 6
- AutoAutonomous task execution with testing and security. Works through all tasks without stopping.Votes: 0GitHub stars: 6
- Autodev InitDerive this project's actual conventions from its code and write them into a project-local rules file, so autodev enforces what this codebase already decided instead of a generic default.Votes: 0GitHub stars: 6
- BrainDrive an authorized product mission from idea through implementation, independent review and live verification. Use when asked to run the fleet, replace manual coordination, or resume Brain.Votes: 0GitHub stars: 6
- FleetShows every Claude Code session on this machine and which ones are blocked on an unanswered question. Use when asked what other sessions are doing, which are waiting, or to open the fleet board.Votes: 0GitHub stars: 6
- Framework RadarResearch coding agents, agent SDKs, orchestration frameworks, harnesses, protocols, evaluations and relevant videos, then execute every selected hypothesis against the current repository. Use when asked what is new, what agent practices are worth testing, or to run the framework radar.Votes: 0GitHub stars: 6
- HealSweep every repo you are working on for vulnerabilities an attacker can actually reach, prove each one is reachable, and fix the ones that survive. One word starts the whole operation.Votes: 0GitHub stars: 6
- IsolateStart work in a fresh git worktree branched from the remote default branch, so parallel agents never share a tree. Use before the first edit of any feature, fix or task, and whenever a repo has more than one session working in it.Votes: 0GitHub stars: 6
- IterateConvergence loop — brainstorm, fix, re-scan until the codebase is clean. Combines brainstorm→apply→auto in one command.Votes: 0GitHub stars: 6
- Learn From FixesRank the failure classes this project actually ships by mining its own fix commits, then propose executable gates for the top ones. Use when the same kind of bug keeps reaching manual QA.Votes: 0GitHub stars: 6
- Marketing RadarResearch current marketing-platform changes and practitioner videos, extract claims with incentives and boundary conditions, then safely execute every selected hypothesis. Use for recurring marketing research, campaign or funnel ideas, and supplied marketing videos.Votes: 0GitHub stars: 6
- PreflightScaffold and grow a project's executable gate file — the checks that run before every deploy and fail the build on the bug families this project actually ships.Votes: 0GitHub stars: 6
- ProveCapture the evidence a change actually works: the BEFORE state while the defect still reproduces, the AFTER state once it passes, both put where a reviewer sees them, so no completion claim rests on the author saying so.Votes: 0GitHub stars: 6
- Rule Ab TestingEvery proposal gets measured against the current approach and at least one variant before it is adopted, and the measurement is reported. Load before recommending a change, writing a detector, or claiming something is cheap, fast, or better.Votes: 0GitHub stars: 6
- Rule Agent ConcurrencyHow many agents to spawn, at which model and effort, so a fan-out does not burn the session's limits. Load before spawning subagents, running a workflow, or dispatching background sessions.Votes: 0GitHub stars: 6
- Rule Design SystemDesign-token rules: semantic tokens over inline colors, where tokens are defined, and the one case hardcoded colors are allowed. Load before writing or editing component styles.Votes: 0GitHub stars: 6
- Rule DiagnosisA wrong fix costs one cycle; a wrong diagnosis costs every cycle until someone questions the premise. Reproduce before explaining, suspect the frame before inventing a mechanism, and attribute a failure before repairing it. Load before proposing any cause, fix, or explanation.Votes: 0GitHub stars: 6
- Rule File OrganizationChoose recoverable paths for generated artifacts. Keep scratch state private, and preserve shared PRD archives, project rules and verification evidence in tracked locations. Load before writing an artifact.Votes: 0GitHub stars: 6
- Rule Gate IntegrityWays a gate or test proves nothing while looking decisive: grading a copy of itself, passing on emptiness, a canary firing for the wrong reason, a summary read as a verdict, a probe pointed at the wrong invocation. Load before writing a gate, a mutation harness, or any check guarding generated output.Votes: 0GitHub stars: 6
- Rule Local FirstVerification happens on this machine, in a browser you drive, before anything is pushed. Covers the local gate, the batched publish cadence, why GitHub Actions is not the gate, and why a restored browser session fakes a pass. Load before verifying, before pushing, and before any visual check.Votes: 0GitHub stars: 6
- Rule Options ProtocolHow a decision panel looks when one is shown: a clickable AskUserQuestion panel of vetted, complementary options with a recommendation in every block. Whether to show one is the operator's decision policy.Votes: 0GitHub stars: 6
- Rule RamificationsThe eight ways a change passes typecheck, build, and a clean console and is still wrong. Derived from 3,127 fix commits across three production repos. Load before implementing a feature and again before calling it done.Votes: 0GitHub stars: 6
- Rule Report ShellThe house shell for any HTML report, audit, or findings page an agent publishes: summary-first cards that expand on click with staggered detail, themed scrollbars, and a token system that survives both themes. Load before writing or editing an HTML page a person will read.Votes: 0GitHub stars: 6
- Rule SecuritySecurity rules this project always applies: secret handling, input validation, parameterized queries, and Supabase RLS. Load before writing code that touches credentials, user input, queries, or auth.Votes: 0GitHub stars: 6
- Rule Thumb FirstInterface design starts from where the hand is and what each element MEANS, not from a palette. Reach zones, progressive density, and the rule that unearned signal destroys real signal. Load before designing a screen, choosing a theme, or adding colour, motion, or output.Votes: 0GitHub stars: 6
- Rule VerificationWhat counts as done for each kind of change: the required verification per task type, and the cross-cutting checks that apply to every task. Load before marking any task complete.Votes: 0GitHub stars: 6
- Rule WindowsWindows-specific development rules: host-aware command wrappers, supervised servers, environment inheritance, native exit status and path conventions. Load only when working on Windows.Votes: 0GitHub stars: 6