All authors

Claude Skills by Eliyce
github.com/Eliyce110 skills4 installs208 views
- Session ResumeReconstruct compact session context from canonical handoff artifacts.Votes: 0GitHub stars: 8
- Spec DiffCompare a new request against the current spec to classify coverage or conflict.Votes: 0GitHub stars: 8
- Spec Quality ReviewOptional pre-pass that surfaces spec defects for a human before freeze.Votes: 0GitHub stars: 8
- Story And Solution WriterTurn scoped work into story and solution artifacts.Votes: 0GitHub stars: 8
- Test Execution Feedback LoopFor each failing test in the verification evidence, propose the smallest fix anchored to file, line, and acceptance criterion.Votes: 0GitHub stars: 8
- Test Per Ac PlannerMap acceptance criteria to specific verification actions.Votes: 0GitHub stars: 8
- Workflow RouterMatch raw prompts to canonical framework workflows before any pipeline phases begin.Votes: 0GitHub stars: 8
- Accessibility ReviewAudit the running UI against WCAG 2.2 A/AA — contrast, focus visibility, keyboard order, ARIA, target size, prefers-reduced-motion. Findings tagged WCAG-2.2.x.x.x.Votes: 0GitHub stars: 8
- Component Conformance ReviewVerify every component in the AST-derived inventory matches its declared spec in components.md. Flag undocumented variants, !important, inline style=, and unwrapped primitives.Votes: 0GitHub stars: 8
- Copy And Ia ReviewAudit voice, tone, labeling, and information architecture against patterns.md.Votes: 0GitHub stars: 8
- Database Design ReviewReview schema and migration changes for integrity and safety.Votes: 0GitHub stars: 8
- Design System CoverageGrade the project's design-system contract for completeness and produce a coverage inventory every downstream design-test skill references. Analog of stride-threat-model.Votes: 0GitHub stars: 8
- Design System SyncSync docs/instructions/design-system/* when a token, component, or breakpoint is added to source. Mirror of canonical-doc-sync.Votes: 0GitHub stars: 8
- Guard InferenceFind and evidence the guards that gate surfaces and transitions — permissions, roles, feature flags, auth and data states — and how each is satisfied, without inventing protection the code does not enforce.Votes: 0GitHub stars: 8
- Index OptimizationReview and improve indexing strategy for changed data paths.Votes: 0GitHub stars: 8
- Journey SynthesisPropose a small set of capped, well-formed journeys over the verified map — one actor, one goal, ordered evidenced steps, dual ends — all marked proposed for human confirmation, never auto-confirmed.Votes: 0GitHub stars: 8
- Map VerificationAdversarially refute or confirm the claims the deterministic checks could not settle — the Tier-B pass over the site map — grounding each verdict in resolving evidence and never rubber-stamping.Votes: 0GitHub stars: 8
- Motion ReviewVerify animations match motion.md budgets and prefers-reduced-motion is respected.Votes: 0GitHub stars: 8
- Query Pattern AnalysisAnalyze query behavior for correctness and performance risk.Votes: 0GitHub stars: 8
- Responsive ReviewVerify declared breakpoints are exercised, no horizontal scroll appears, touch targets meet spec, and RTL parity holds when declared.Votes: 0GitHub stars: 8
- Root Cause AnalysisGenerate a canonical RCA artifact for an incident or failure.Votes: 0GitHub stars: 8
- Site Map AssemblyDrive the compile verb that folds the surface, transition, and guard layers into app-map.yaml, and resolve merge conflicts against the locked committed content without overwriting curated entries.Votes: 0GitHub stars: 8
- Site Map Gap AnalysisTurn the graph invariants and verification verdicts into stable SM-* findings and a gap report, so the map's problems are triaged, evidenced, and each carry a concrete fix.Votes: 0GitHub stars: 8
- Site Map MaintainerKeep the site map fresh during a feature-development change — when a diff touches flow-relevant files, patch just the affected surfaces so the map never drifts from the code it describes.Votes: 0GitHub stars: 8
- Site Map ReadinessGrade whether the project is mappable — app kind, frameworks, and an extractor that covers its shape — and route the unmappable case before any other site-map skill runs.Votes: 0GitHub stars: 8
- Site Map RetestRe-check the stored site map against the current code by running the same verification again — never invent a finding, never soften one, never call the absence of proof a fix.Votes: 0GitHub stars: 8
- State Coverage ReviewVerify every component in the AST inventory implements its declared states (default/hover/focus/disabled/loading/error/empty) and is exercised by Playwright tests.Votes: 0GitHub stars: 8
- Surface ExtractionRun the extractors, normalize the raw surfaces, and fingerprint the result so the site-map run has a deterministic, evidence-backed inventory of what the app exposes.Votes: 0GitHub stars: 8
- Surface ModelingTurn raw extracted surfaces into named, typed, module-attributed surfaces with entry and exit marks — the non-inferable layer the engine cannot derive from the code alone.Votes: 0GitHub stars: 8
- Token Conformance ReviewDetect hard-coded design values (hex, raw px/rem, ad-hoc font stacks) in UI source that should resolve to a declared token. High severity by default.Votes: 0GitHub stars: 8
- Transition TracingFind and evidence the transitions between surfaces — where navigation actually goes, what triggers it, and the file:line that proves it — without inventing edges from mere links.Votes: 0GitHub stars: 8
- Ui Doc MaintainerMaintain UI screens, components, and state docs after UI changes.Votes: 0GitHub stars: 8
- User Flow GenerationGenerate or update user flows for UI-facing features.Votes: 0GitHub stars: 8
- Ux Design ResearchResearch external UI references for full-lane UI work.Votes: 0GitHub stars: 8
- Ux Heuristic EvaluationEvaluate UI behavior against usability heuristics.Votes: 0GitHub stars: 8
- Ux State MachineDefine interface states and transitions for UI-heavy work.Votes: 0GitHub stars: 8
- Regression Test GenSuggest regression coverage for changed stack behavior.Votes: 0GitHub stars: 8
- Content PlannerShape a writing task into an outline, brief, sequence, or publishable plan. Use when a content request needs structure (audience, goal, outline, success metric) before drafting.Votes: 0GitHub stars: 8
- Content ReviewerReview drafts for clarity, structure, evidence quality, and reader usefulness against the project's writing rules. Use when a draft needs a structured review pass before publishing.Votes: 0GitHub stars: 8
- Content WriterProduce reader-ready drafts for docs, briefs, landing pages, and internal writing deliverables, starting from a brief and ending in style-compliant prose. Use when an approved brief needs to become a publishable draft.Votes: 0GitHub stars: 8
- Script WriterWrite concise spoken-word scripts and narrative sequences optimized for pacing, transitions, and spoken clarity. Use when the deliverable will be performed aloud (video, podcast, demo).Votes: 0GitHub stars: 8
- Seo OptimizerRevise drafts for search visibility — keyword placement, heading hierarchy, meta fields, internal links — without sacrificing readability. Use after the draft is reader-ready and before publishing.Votes: 0GitHub stars: 8
- Style EnforcerNormalize drafts to the project's explicit writing style and formatting rules at docs/instructions/rules/writing-style.md. Use as the last pass before publish.Votes: 0GitHub stars: 8
- Auth Mechanism ReviewReason about authentication weaknesses including JWT vulnerabilities, session security, OAuth/OIDC flaws, brute-force surfaces, and password storage from code and docs evidence.Votes: 0GitHub stars: 8
- Business Logic Abuse ReviewDerive abuse cases from module docs and validate them against tests and runtime evidence.Votes: 0GitHub stars: 8
- Cryptographic ReviewIdentify cryptographic failures including weak hashing, insecure encryption modes, hardcoded keys, weak PRNG usage, and disabled TLS verification from code evidence.Votes: 0GitHub stars: 8
- Dependency Advisory TriageNormalize dependency advisories across native audits and OSV evidence.Votes: 0GitHub stars: 8
- Input Validation ReviewReason about SSRF, IDOR, mass assignment, injection vectors, file upload abuse, prototype pollution, and ReDoS from code and docs evidence.Votes: 0GitHub stars: 8
- Logging Monitoring ReviewAssess security logging and monitoring gaps including missing audit trails, log injection surfaces, sensitive data in logs, and alerting coverage.Votes: 0GitHub stars: 8
- Permission Boundary ReviewReview authorization, tenant isolation, and privileged route boundaries.Votes: 0GitHub stars: 8