ChloeVPin
- 35 skills
- 0 followers
- 20 hours ago last updated
- ▌ Epistemic Coding · chloevpinApply an evidence-first philosophy while investigating, changing, or explaining a software repository. Use when correctness, uncertainty, scope, or the evidence behind a coding decision matters.
- ▌ Safe Git Workflow · chloevpinUse Git safely while an AI coding agent investigates, edits, reviews, commits, rebases, merges, or publishes repository changes. Use when branch state, uncommitted work, history, conflicts, or destructive commands could affect recoverability or collaboration.
- ▌ Accessibility Review · chloevpinReview user-facing software changes for accessibility barriers across semantics, keyboard and other input, focus, structure, content, feedback, and assistive technology behavior. Use for web, mobile, desktop, CLI, and interactive UI changes; adapt the checks to the platform.
- ▌ Secure Coding Review · chloevpinReview an AI-generated coding change for application security risks at trust boundaries, including input handling, authorization, secrets, data exposure, injection, and unsafe failure behavior. Use before accepting security-relevant features, bug fixes, or refactors.
- ▌ Skill Quality Review · chloevpinReview a proposed or existing SKILL.md before publication for practical scope, precise triggers, evidence quality, counterexamples, safety, overlap, composability, and honest lifecycle status. Use when creating, revising, promoting, deprecating, or merging agent skills.
- ▌ Data Migration Safety · chloevpinDesign and review database, schema, storage, and data migrations for correctness, compatibility, observability, rollback limits, and safe recovery. Use when an AI coding agent changes persisted data, schemas, indexes, formats, or migration scripts.
- ▌ Knowledge Maintenance · chloevpinKeep coding-agent skills and guidance current by tracking provenance, freshness, deprecation, supersession, contradictions, and review triggers. Use when evidence, dependencies, versions, or failures change.
- ▌ Build And CI Integrity · chloevpinReview and improve build systems and CI workflows for reproducibility, least privilege, trustworthy artifacts, controlled inputs, and repeatable verification. Use when an AI coding agent changes build commands, workflow files, runners, artifact publication, release checks, or provenance.
- ▌ Regression Test Design · chloevpinDesign focused regression tests for AI-generated or human software changes from observable behavior, failure modes, and boundaries. Use when fixing a bug, adding behavior, changing an interface, or strengthening a weak test suite.
- ▌ Repository Exploration · chloevpinMap an unfamiliar software repository before changing it. Use when an AI coding agent must locate the right files, understand callers and conventions, identify verification commands, or avoid missing hidden interfaces and generated code.
- ▌ Implementation Planning · chloevpinTurn verified coding requirements into a minimal, dependency-aware implementation plan with risks, verification evidence, and stopping conditions. Use before multi-file, cross-boundary, risky, or ambiguous AI coding-agent changes.
- ▌ Contradiction Resolution · chloevpinResolve conflicting claims, evidence, tests, or failures without forcing false consensus. Use when sources or observed behavior disagree and the coding agent must preserve uncertainty and decision boundaries.
- ▌ Tool Authorization Audit · chloevpinReview AI-agent tools and proposed calls for least privilege, bounded parameters, explicit authorization, isolation, and auditable high-impact actions. Use when tools, credentials, scopes, or permissions change.
- ▌ Dependency Security Audit · chloevpinReview dependency and supply-chain changes for provenance, vulnerabilities, integrity, execution behavior, and residual risk. Use when manifests, lockfiles, build scripts, or external artifacts change.
- ▌ Differential Patch Review · chloevpinCompare a candidate coding change with a trusted baseline or reference to detect observable behavioral divergence. Use when ordinary tests pass but semantic alignment remains uncertain.
- ▌ Evidence Driven Debugging · chloevpinDiagnose software failures by reproducing the symptom, separating observations from hypotheses, testing competing explanations, and making the smallest verified fix. Use for bugs, regressions, flaky behavior, failing builds, and unexplained runtime errors in AI coding-agent work.
- ▌ Privacy And Data Handling · chloevpinReview software changes that collect, use, store, transmit, log, infer, share, or delete personal or sensitive data. Use to reduce privacy risk through purpose limitation, minimization, access control, retention, redaction, and lifecycle-aware design.
- ▌ API Contract Compatibility · chloevpinDesign, change, or review APIs and serialized interfaces while making compatibility, versioning, errors, and migration behavior explicit. Use for HTTP, RPC, CLI, event, library, configuration, and file-format interfaces used by other code or people.
- ▌ Requirements To Acceptance · chloevpinTurn an ambiguous software request into explicit, testable acceptance criteria before an AI coding agent changes a repository. Use for feature requests, bug reports, refactors, migrations, and tasks with hidden assumptions or unclear boundaries.
- ▌ Prompt Injection Resistance · chloevpinProtect AI coding agents from instructions hidden in repository files, issues, documents, web pages, tool output, model context, or memory. Use whenever an agent reads untrusted content, retrieves external context, summarizes data, or proposes an action based on mixed instructions and data.
- ▌ Release And Rollback Safety · chloevpinPlan and review safe software releases with explicit preconditions, staged exposure, health signals, rollback boundaries, and recovery evidence. Use when an AI coding agent changes deployable behavior, migrations, configuration, or release automation.
- ▌ Resilience And Retry Design · chloevpinDesign and review timeouts, retries, backoff, circuit breakers, rate limits, bulkheads, and graceful degradation for unreliable dependencies. Use when an AI coding agent changes network calls, queues, workers, caches, or failure handling.
- ▌ Test Effectiveness Analysis · chloevpinEvaluate whether tests detect acceptance-relevant behavioral faults using boundaries, negative cases, differential checks, and mutation-oriented diagnostics. Use when tests are added, changed, weak, or contradicted by regressions.
- ▌ Architecture Decision Making · chloevpinEvaluate and record software architecture choices using constraints, alternatives, evidence, decision boundaries, and reversible consequences. Use when an AI coding agent changes system boundaries, data ownership, integration patterns, concurrency models, or long-term structure.
- ▌ Concurrency And Shared State · chloevpinDesign, debug, or review concurrent and asynchronous code for race freedom, state invariants, ordering, cancellation, resource ownership, and failure recovery. Use when an AI coding agent changes threads, tasks, queues, locks, caches, events, retries, or shared mutable state.
- ▌ Dead Code And Comment Cleanup · chloevpinIdentify dead code, duplicated literals, drift-prone declarations, and comments that restate implementation without deleting anything until usage and intent are verified. Use when an AI coding agent is asked to clean up unused code or redundant comments.
- ▌ Skill Composition And Routing · chloevpinSelect, order, and combine skills for an AI coding-agent task without activating irrelevant, duplicate, or conflicting guidance. Use when several skills may apply, a workflow spans phases, or a skill library is being extended.
- ▌ Repository Change Verification · chloevpinVerify that an AI-generated repository change matches the requested outcome, preserves unrelated behavior, and has adequate evidence before acceptance. Use for patches, commits, and pull requests.
- ▌ Behavior Preserving Refactoring · chloevpinRestructure code without changing its observable contract. Use when an AI coding agent extracts modules, renames interfaces, reduces duplication, changes control flow, or modernizes implementation while behavior should remain stable.
- ▌ Performance Regression Analysis · chloevpinInvestigate and validate software performance changes using representative workloads, baselines, variance-aware measurements, and resource tradeoffs. Use when an AI coding agent is asked to make code faster, reduce latency or cost, increase throughput, or diagnose a performance regression.
- ▌ Static Analysis And Type Safety · chloevpinUse linters, type checkers, security analyzers, and other static checks as evidence while changing a codebase. Use when fixing diagnostics, introducing types, changing analyzer configuration, or deciding whether a warning is real, irrelevant, or dangerous to suppress.
- ▌ Configuration And Secrets Safety · chloevpinDesign and review application configuration, environment handling, and secret use without unsafe defaults, accidental disclosure, or environment drift. Use when an AI coding agent changes config files, environment variables, deployment settings, credentials, keys, or feature flags.
- ▌ Agent Evaluation And Benchmarking · chloevpinDesign and interpret evaluations of AI coding-agent behavior across realistic tasks, correctness, safety, usefulness, and maintainability. Use when creating benchmarks, comparing agents or skills, measuring regressions, or making claims about agent capability.
- ▌ Observability And Instrumentation · chloevpinAdd or review logs, metrics, traces, and diagnostic signals so AI coding agents can understand real behavior and failures without excessive cost, noise, or data exposure. Use when changing production behavior, debugging intermittent issues, or operating asynchronous and distributed code.
- ▌ Internationalization And Localization · chloevpinDesign and review software for multiple languages, locales, scripts, regions, calendars, currencies, units, and text directions. Use when an AI coding agent adds user-facing text, formatting, sorting, input, translation, or locale-sensitive behavior.