All authors
Claude Skills by OutlineDriven
github.com/OutlineDriven865 skills3 installs846 views
- Firebase Apk ScannerUse when an authorized user needs to assess mobile-backend exposure from compiled Android APKs, covering Firebase, custom HTTP backends, and cloud function endpoints. Human-only invocation.Votes: 0GitHub stars: 52
- First Load Byte ReductionUse when a first screen needs lower transfer bytes without visual or behavioral change. Not for visual redesign or behavioral changes.Votes: 0GitHub stars: 52
- Fix P0 IssuesUse when the user asks to fix P0s, address critical issues, or work on priorities from the weekly product briefing. Don''t use for non-P0 issues or local bug fixes.Votes: 0GitHub stars: 52
- Fixed View Visual BenchmarkUse when a visual needs repeatable fixed-view rendering and independent rubric scoring. Not for free-form visual review or subjective critique.Votes: 0GitHub stars: 52
- Frame Rate StabilityUse when a rendering path needs stable frame-time, CPU, GPU, and memory evidence against fixed targets. Not for one-shot profiling or visual quality review.Votes: 0GitHub stars: 52
- Framing Divergence FanoutUse when a user suspects the current direction is tunnel-visioned or inherited its framing: spawn 2-5 independent reads, classify each, cluster by shared root, and surface divergent-incompatible reads first. Not for framing-bias checks on a question — use prism.Votes: 0GitHub stars: 52
- Fresh Reader ReviewUse when asked to cold-read an artifact with fresh zero-context eyes and cut whatever a stranger cannot follow. Not for criteria-review of requirements docs: use doc-review.Votes: 0GitHub stars: 52
- From Breaking PerspectiveUse when a user wants an answer only from the breaking seat (stakeholders, dependencies, accounting, compatibility under destructive pressure). A breaking-perspective answer is emitted without blending. Not for any other from-* lens seat or multi-lens synthesis.Votes: 0GitHub stars: 52
- From Business PerspectiveUse when the user wants an answer only from the business seat, to produce a business-perspective analysis of money, customers, and timing without blending other lenses. Not for any other from-* lens seat or multi-lens synthesis.Votes: 0GitHub stars: 52
- From Career PerspectiveUse when a user wants an answer only from the career seat (effects on human trajectories). Emits a career-perspective analysis without blending other lenses. Not for any other from-* lens seat or multi-lens synthesis.Votes: 0GitHub stars: 52
- From Codebase PerspectiveUse when asked to answer only from the codebase seat: what existing code tolerates or punishes. Emits a single-perspective analysis without blending. Not for rebuilding from primitives — use from-first-principle. Read-only; no source or remote mutation.Votes: 0GitHub stars: 52
- From First PrincipleUse when a user wants to rebuild a design, organization, or API from primitives. Not for a perspective take: use from-perspective.Votes: 0GitHub stars: 52
- From Human PerspectiveUse when a user wants an answer only from the human seat: what a person can love, trust, and tolerate. Emits a human-perspective analysis without blending. Not for rebuilding from primitives — use from-first-principle. Read-only; no source or remote mutation.Votes: 0GitHub stars: 52
- From Impact PerspectiveUse when asked to answer only from the impact seat: who and what actually moves. Returns an impact-perspective analysis without blending. Not for rebuilding from primitives — use from-first-principle. Read-only; no source or remote mutation.Votes: 0GitHub stars: 52
- From Innovation PerspectiveUse when the user wants an answer only from the innovation seat: original technique, talent, and culture. Emits an innovation-perspective analysis without blending. Not for rebuilding from primitives — use from-first-principle. Read-only; no source or remote mutation.Votes: 0GitHub stars: 52
- From Moat PerspectiveUse when the user wants an answer only from the moat seat: building, keeping, and thickening defensibility. Emits a moat-perspective analysis without blending. Not for rebuilding from primitives — use from-first-principle. Read-only; no source or remote mutation.Votes: 0GitHub stars: 52
- From Rentseeking PerspectiveUse when the user wants an answer only from the rent-seeking seat: extraction without building. Emits a rent-seeking-perspective analysis without blending. Not for rebuilding from primitives — use from-first-principle. Read-only; no source or remote mutation.Votes: 0GitHub stars: 52
- From Skeptic PerspectiveUse when a user wants an answer only from the skeptic seat: cold reasoning without project loyalty. Emits a skeptic-perspective analysis without blending. Not for rebuilding from primitives — use from-first-principle. Read-only; no source or remote mutation.Votes: 0GitHub stars: 52
- From Stability PerspectiveUse when the user wants an answer only from the stability seat: preservation of the working machine. Emits a stability-perspective analysis without blending. Not for rebuilding from primitives — use from-first-principle. Read-only; no source or remote mutation.Votes: 0GitHub stars: 52
- FromzeroUse when replacing a greenfield attempt with a clean pad of verified requirements. Not for rebuilding from primitives: use from-first-principle. Requires a committed, VCS-recoverable attempt.Votes: 0GitHub stars: 52
- Frontend Design DeslopUse when a user builds or styles a web frontend or asks to make it not look AI-generated. Not for component-level UI work without the token system: use frontend-ui-engineering.Votes: 0GitHub stars: 52
- Frontend Fidelity RebuildUse when an authorized reference surface needs a clean-room frontend reconstruction across static, motion, and responsive fidelity. Not for styling or component work without a reference surface.Votes: 0GitHub stars: 52
- Frontend Ui EngineeringUse when asked to build or modify production-quality components, layouts, state, and pages with WCAG 2.1 AA and real content. Not for token-system design: use frontend-design-deslop.Votes: 0GitHub stars: 52
- Full Product EvaluationUse when a complete product needs production-like acceptance evidence against documented acceptance criteria. Not for single-component evaluation or evaluation without documented criteria.Votes: 0GitHub stars: 52
- Function Audit Context AnalyzerUse when asked for audit-context analysis of one function, or to build audit context across codebase before vulnerability hunting. Local write only. Not for vulnerability finding or severity rating.Votes: 0GitHub stars: 52
- Fuzz Harness WritingUse when a user needs to create or improve a deterministic, engine-agnostic fuzz harness for raw or structured target inputs. Not for coverage measurement: use fuzzing-coverage-analysis.Votes: 0GitHub stars: 52
- Fuzzing Coverage AnalysisUse when a user needs to measure fuzz corpus coverage, explain a coverage plateau, or turn uncovered regions into campaign work. Not for harness creation: use fuzz-harness-writing.Votes: 0GitHub stars: 52
- Fuzzing DictionaryUse when a parser, protocol, or file format fuzzer stalls at fixed-token validation gates and needs a coverage dictionary. Not for patching the SUT: use fuzzing-obstacles.Votes: 0GitHub stars: 52
- Fuzzing ObstaclesUse when asked to identify and bypass checksums, nondeterminism, or validation barriers that block fuzzing coverage. Not for dictionary creation: use fuzzing-dictionary. Local writes only.Votes: 0GitHub stars: 52
- Gate And MergeUse when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.Votes: 0GitHub stars: 52
- Gate Proposed ChangeUse when asked to evaluate a proposed commit, merge, or auto-merge against a gate config. Not for landing PRs: use gate-and-merge. Read-only.Votes: 0GitHub stars: 52
- Genealogical ProofUse when a genealogical identity or relationship needs correlation, conflict analysis, and negative-search proof. Not for non-genealogical identity proof.Votes: 0GitHub stars: 52
- GeneralizeUse when asked to derive the general rule a request carries as examples instead of a stated rule, then bound it. Not for ambiguity in a stated request: use askme. Read-only.Votes: 0GitHub stars: 52
- Generate My TasteUse when asked to generate a personal taste skill from local evidence. Not for applying an existing taste register: use the user-private spine skill.Votes: 0GitHub stars: 52
- Get Pr CommentsUse when asked to summarize feedback on the active PR. Returns severity-grouped feedback and an action list. Not for finding PRs to review — use gh-review-requests. Not for resolving feedback — use resolve-pr-feedback. Read-only.Votes: 0GitHub stars: 52
- Gh Review RequestsUse when the user asks to find PRs to review or check the team review queue. Not for summarizing or resolving feedback on a specific PR: use resolve. Read-only.Votes: 0GitHub stars: 52
- Gha Security ReviewUse when asked to review GitHub Actions for exploitable vulnerabilities, including prompt injection through Claude Code Action, Gemini CLI, or OpenAI Codex. Read-only. Not for general security review.Votes: 0GitHub stars: 52
- Git BranchlessUse when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.Votes: 0GitHub stars: 52
- Git CleanupUse when the user explicitly invokes branch or worktree cleanup for a repo with accumulated local branches. Don''t use for remote branch deletion or force-push operations.Votes: 0GitHub stars: 52
- Git GuardrailsUse when a repository needs Git safety controls: guard destructive commands, set up gitignore or fix gitignore when untracked files keep appearing, or install or repair a repository-local pre-commit hook from project gates, including package-manager-native commit-time checks. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Git History AnalysisUse when the user asks about recent engineering work, what the team is working on, planning or roadmap material, or an explicitly requested Slack summary. Not for remote or irreversible changes.Votes: 0GitHub stars: 52
- Git Workflow And VersioningUse when the user asks for release, version bump, changelog, or branch workflow beyond a single commit. Don''t use for single commits or for publishing to a package registry.Votes: 0GitHub stars: 52
- Github Backlog TriageUse when the user invokes backlog triage for a GitHub repo''s open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.Votes: 0GitHub stars: 52
- Github Bug Report TriageUse when evaluating whether a bug issue has sufficient detail and identifying missing reporter information. Not for non-bug issues or backlog triage: use github-backlog-triage.Votes: 0GitHub stars: 52
- Github Issue DedupeUse when finding duplicate GitHub issues or checking for similar issues against a target issue. Not for closing, labeling, or modifying any duplicate issue.Votes: 0GitHub stars: 52
- Github Solution ResearchUse when a bug, integration failure, dependency issue, unclear API usage, implementation blocker, or tool-capability need calls for GitHub solutions. Not for source or remote-system changes.Votes: 0GitHub stars: 52
- Goal InitUse when a durable effort needs an approved, checkable success predicate before work starts. Not for requirement-to-evidence ledgers. Never remote, credential, publish, deploy, or irreversible.Votes: 0GitHub stars: 52
- Goal Prompt DraftingUse when asked to draft copy-ready /goal objectives for long-running agents. Not for source or remote-system changes.Votes: 0GitHub stars: 52
- Good ReadmeUse when the user asks to create, rewrite, review, or polish an open-source README, including shop-window READMEs. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Graph BackboneUse when defining, revising, or gate-replanning the project structural backbone in project-root graph.yaml. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52