JovaniPink
- 79 skills
- 0 followers
- 9 hours ago last updated
- ▌ Workflow Retrospective · jovanipink bundleReview a completed or paused workflow using supplied artifacts and current task evidence to identify what helped, what failed, why, and which bounded improvement to test next. Invoke explicitly after meaningful work; do not mine private histories or automatically rewrite policy or skills.
- ▌ Agent Evaluation Design · jovanipink bundleDesign an evaluation contract for an AI agent, model-assisted workflow, or prompt-driven system using representative cases, baselines, configurations, graders, error classes, thresholds, cost, latency, human review, and limitations. Use when the decision depends on measured AI behavior across cases; use test-strategy for ordinary software coverage and test-quality-review for an existing test suite.
- ▌ Decision Evidence Trace · jovanipink bundleMaintain a bounded decision and evidence trail for a long-running task without exposing hidden reasoning, raw transcripts, secrets, or unrelated activity. Invoke explicitly when the user wants an auditable task log in chat or an authorized append-only file.
- ▌ Implementation Planning · jovanipink bundleProduce a decision-complete implementation plan grounded in repository and platform evidence. Use when a change needs concrete interfaces, ordered steps, tests, rollout controls, checkpoints, and stopping conditions before work begins.
- ▌ Kpi Outcome Measurement · jovanipink bundleDesign or review outcome measurement with precise definitions, units, populations, baselines, targets, data authority, and decision use. Use when a program or product needs measures that distinguish activity, output, outcome, and impact.
- ▌ Module Interface Design · jovanipink bundleDesign or review a module boundary, vocabulary, interface, and hidden implementation so callers face a smaller and more stable contract. Use when code is coupled, concepts leak across layers, responsibilities are unclear, or a redesign needs concrete options before implementation.
- ▌ Skill Import Provenance · jovanipink bundleReview provenance before transferring Jovani-owned skill material between authorized repositories or distributions. Invoke explicitly for an owned-source transfer or a decision about whether proposed external skill material must be rejected; third-party skill catalogs are never implementation sources.
- ▌ Change Adoption Planning · jovanipink bundlePlan organizational or product change around affected people, behavior, capability, incentives, support, measurement, and feedback. Use when technical delivery alone will not produce the intended operating outcome.
- ▌ Data Migration Readiness · jovanipink bundleReview a proposed data or schema migration for authority, compatibility, sequencing, reconciliation, rollback, and operational evidence. Use before a migration or cutover; do not execute or ratify the migration.
- ▌ Functional Motion Review · jovanipink bundleReview whether interface motion clarifies evidence, sequence, comparison, or reader actions. Use for animated editorial and data experiences; not for routine styling, implementing animation, or claiming engagement from visual polish.
- ▌ Portable Skill Authoring · jovanipink bundleDesign or revise a portable Agent Skill with precise routing, invocation policy, focused references, provenance, security boundaries, evals, and generated client adapters. Use for cross-client SKILL.md catalog work; do not trigger for ordinary documentation or client-specific command files.
- ▌ Source Grounded Research · jovanipink bundleResearch a question using current primary sources, preserving publisher URLs, dates, units, provenance, and uncertainty. Use for web investigations, fact checks, comparisons, or recommendations where current evidence and precise attribution matter.
- ▌ Authority Boundary Review · jovanipink bundleReview a system or migration to identify authoritative stores, exact-byte custody, projections, writers, readers, reconciliation paths, and ratified versus proposed contracts. Use for data architecture, migration, integration, and source-of-truth decisions.
- ▌ Cross Stack Quality Gates · jovanipink bundleDiscover and run the repository's real validation gates across supported application, language, data, and infrastructure stacks without assuming a universal command. Use after changes, before review, or when asked whether a codebase passes its checks.
- ▌ Finish Development Branch · jovanipink bundleReconcile a development branch and present evidence-based options for pull request, merge, retention, or cleanup. Invoke explicitly when implementation is complete enough to decide the branch's next state without assuming push, merge, deletion, or abandonment authority.
- ▌ Multi Agent Orchestration · jovanipink bundleCoordinate authorized parallel agents on independent bounded tasks with explicit ownership, evidence contracts, cost awareness, and final reconciliation. Invoke explicitly when parallel work can reduce latency without creating edit collisions or delegating irreversible decisions.
- ▌ Acceptance Evidence Ledger · jovanipink bundleCreate or update an acceptance ledger for substantial work that needs explicit outcomes, current evidence, re-verification, and visible blockers or abandonments. Invoke explicitly when a user requests an inline or repository-owned completion contract; use focused testing, execution, or claim-verification skills for one-time requests.
- ▌ Context Reliability Review · jovanipink bundleReview the reliability of context assertions supplied to an AI system by tracing provenance, authority, freshness, effective and recorded time, permissions, conflicts, supersession, and revocation. Use when agent behavior depends on whether contextual claims are current and allowed; use authority-boundary-review for system-of-record architecture rather than assertion-level context.
- ▌ Domain Vocabulary Modeling · jovanipink bundleBuild a proposed domain vocabulary from current code, documents, and stakeholder language, including concepts, definitions, relationships, invariants, authorities, examples, and contradictions. Use when inconsistent terms are causing design or communication errors; do not treat the result as ratified without owner evidence.
- ▌ Python Engineering Profile · jovanipink bundleApply focused Python engineering judgment after repository gate discovery. Use for Python packages, typing, async behavior, tests, dependencies, compatibility, and builds; defer exact commands to repository evidence.
- ▌ Application Security Review · jovanipink bundleReview application or service security against current threat evidence and verifiable control requirements. Use for read-only assessment of authentication, authorization, input handling, data protection, session, error, configuration, and abuse risks; do not use this skill to audit agent packages.
- ▌ Decision Governance Records · jovanipink bundleCreate or review decision records that preserve context, options, evidence, ownership, status, consequences, and review triggers. Use when a proposal must be distinguished from a ratified, rejected, superseded, or unresolved decision.
- ▌ Workshop Planning Synthesis · jovanipink bundlePlan a workshop around a concrete decision or learning outcome, then synthesize its evidence without manufacturing consensus. Use for agendas, facilitation structure, prework, participation, decisions, actions, and follow-up.
- ▌ Operational Readiness Review · jovanipink bundleReview whether a service or application is operationally ready for release and sustained ownership. Use for read-only assessment of objectives, dependencies, monitoring, alerts, capacity, failure handling, incidents, runbooks, recovery, and support boundaries.
- ▌ Production Incident Analysis · jovanipink bundleAnalyze a production incident using timestamped evidence, system behavior, contributing conditions, response actions, and recovery. Use after an incident to establish what happened, why controls failed, and what learning or remediation is justified.
- ▌ Adobe Aem Engineering Profile · jovanipink bundleApply focused Adobe Experience Manager engineering judgment after repository gate discovery. Use for AEM as a Cloud Service or AEM 6.5 code, Sling and OSGi, content packages, Dispatcher, caching, tests, compatibility, and builds; preserve separate Cloud Manager authority.
- ▌ High Signal Technical Writing · jovanipink bundleEdit technical prose for clarity, evidence density, specificity, rhythm, and audience fit while preserving meaning and repository voice. Use for completion reports, status updates, or documentation that sounds vague, repetitive, promotional, or machine-generic; do not use style heuristics as evidence of authorship.
- ▌ Iteration Postlaunch Learning · jovanipink bundlePlan and synthesize postlaunch learning from observed behavior, incidents, feedback, experiments, and outcome measures. Use after a release when the team must decide what to retain, change, investigate, or stop.
- ▌ Merge Conflict Reconciliation · jovanipink bundleReconcile an active Git merge, rebase, or cherry-pick conflict by inspecting exact repository state, preserving both sides' intent, validating the result, and keeping abort available. Invoke explicitly for an identified conflicted worktree; staging, continuing, committing, and pushing require separate authority.
- ▌ Terraform Engineering Profile · jovanipink bundleApply focused Terraform engineering judgment after repository gate discovery. Use for modules, providers, state, plans, upgrades, compatibility, and infrastructure review; validation never implies apply authority.
- ▌ Agentic System Security Review · jovanipink bundleReview an agentic system across agent identity, models, instructions, tools, memory, retrieval, delegation, protocols, guardrails, outputs, supply chain, cost, revocation, and emergency stopping. Use for a read-only threat and control assessment of model-mediated actions; use application-security-review for conventional application controls and skill-security-review for a skill package.
- ▌ Dependency Supply Chain Review · jovanipink bundleReview software dependencies and build supply-chain evidence for provenance, integrity, maintenance, vulnerability, and compromise risk. Use for a read-only assessment of manifests, lockfiles, registries, build inputs, CI actions, artifacts, and update policy.
- ▌ Design Rationale Investigation · jovanipink bundleInvestigate why code, architecture, or an operational design exists by comparing direct historical evidence, current behavior, and competing hypotheses. Use for design history and rationale questions; do not infer intent from code shape alone or search unrelated private sources.
- ▌ Google Adk Engineering Profile · jovanipink bundleReview or design a Google Agent Development Kit system using exact framework, language, model, session, tool, evaluation, and deployment evidence. Use for human-facing ADK architecture and version discovery; combine it with the focused agent security, evaluation, context, retrieval, and operational skills instead of treating framework defaults as proof of safety or readiness.
- ▌ PHP Drupal Engineering Profile · jovanipink bundleApply focused PHP and Drupal engineering judgment after repository gate discovery. Use for Composer projects, Drupal modules or themes, entity and configuration APIs, caching, security, tests, compatibility, and builds; defer exact commands to repository evidence.
- ▌ Public Private Boundary Review · jovanipink bundleReview code, documentation, examples, articles, or release artifacts before public exposure to find secrets, internal identifiers, private operational details, proprietary material, and claims unsupported by public evidence. Use before open-sourcing or publishing work derived from mixed public and private contexts.
- ▌ Java Spring Engineering Profile · jovanipink bundleApply focused Java and Spring engineering judgment after repository gate discovery. Use for JVM services, Spring Boot applications, concurrency, transactions, tests, dependencies, compatibility, and builds; honor repository wrappers and toolchains.
- ▌ Source Output Conformance Audit · jovanipink bundleAudit whether exact source identity and expected values survive parsing or extraction, validation, persistence, and readback using source-cited oracles and mutation-sensitive tests. Use for end-to-end source-to-output fidelity claims; use test-quality-review for test-suite quality and authority-boundary-review for ownership architecture alone.
- ▌ Agent Context State Memory Design · jovanipink bundleDesign or review how an agent separates prompt context, session events, scoped state, long-term memory, and artifacts. Use when identity, authority, freshness, retention, provenance, tenant isolation, poisoning, or deletion behavior could change what an agent knows or does; use context-reliability-review for a supplied context packet rather than the hosting architecture.
- ▌ Agent Tool Action Boundary Review · jovanipink bundleReview the boundary between an agent and its registered tools or actions, including identity, permissions, schemas, argument controls, network reach, confirmation, idempotency, replay protection, rollback, and audit evidence. Use before an agent can read sensitive data or cause an external effect; use application-security-review for broader application controls.
- ▌ API Contract Compatibility Review · jovanipink bundleReview API, event, schema, and client changes for backward, forward, and rollout compatibility. Use when producers and consumers may upgrade independently or when a change can alter behavior, shape, timing, errors, or semantics.
- ▌ Csharp Dotnet Engineering Profile · jovanipink bundleApply focused C# and .NET engineering judgment after repository gate discovery. Use for .NET applications, libraries, ASP.NET Core, Entity Framework Core, async behavior, tests, packages, compatibility, and builds; defer exact commands to repository evidence.
- ▌ Performance Scalability Diagnosis · jovanipink bundleDiagnose latency, throughput, resource, contention, and scalability problems using measured evidence and competing hypotheses. Use when a system is slow, unstable under load, or approaching a capacity boundary; do not silently optimize code.
- ▌ Research To Publication Lifecycle · jovanipink bundleCoordinate an explicitly requested source-to-publication learning lifecycle across research, evidence tracing, model or forecast evaluation, corrections, and retrospective findings. Invoke explicitly when the user wants traceable knowledge objects or a public-safe research index; do not use for a one-off search, ordinary summary, or automatic publication.
- ▌ Swift Swiftui Engineering Profile · jovanipink bundleApply focused Swift and SwiftUI engineering judgment after repository gate discovery. Use for packages, applications, concurrency, UI state, tests, compatibility, and builds; require observed macOS evidence for Apple toolchain claims.
- ▌ Postgresql SQL Engineering Profile · jovanipink bundleApply focused PostgreSQL and SQL engineering judgment after repository gate discovery. Use for schemas, queries, transactions, migrations, indexing, compatibility, and database test concerns; never mutate shared data merely to validate.
- ▌ Retrieval Grounding Quality Review · jovanipink bundleReview whether an agent retrieval and grounding system selects authorized, current, relevant evidence and produces claims that the evidence actually supports. Use for corpus authority, tenant filtering, retrieval metrics, citation support, abstention, poisoning, and injection; use source-grounded-research for a human research task and source-output-conformance-audit for deterministic source-to-output transformation.
- ▌ Cross Capability Dependency Mapping · jovanipink bundleMap dependencies across products, teams, data, platforms, decisions, and operating capabilities. Use when delivery or outcomes depend on multiple owners and hidden sequencing, authority, or failure paths must be made explicit.
- ▌ Salesforce Apex Engineering Profile · jovanipink bundleApply focused Salesforce, Apex, and Lightning Web Components engineering judgment after repository gate discovery. Use for metadata projects, packages, governor limits, data access, tests, compatibility, and deployment readiness; preserve separate live-org authority.
- ▌ Stakeholder Technical Communication · jovanipink bundleTranslate technical evidence for a named stakeholder decision without overstating certainty, hiding risk, or exposing inappropriate detail. Use for executive summaries, review packets, status updates, decision briefs, and cross-functional explanations.
- ▌ Value Attribution Evidence Maturity · jovanipink bundleAssess claimed value, benefit, savings, risk reduction, or outcome contribution against an explicit evidence-maturity model. Use when stakeholders need to distinguish observed results, estimates, attribution, contribution, and causal claims.
- ▌ Data Authority Migration Ratification · jovanipink bundlePrepare a proposed data-authority and migration decision record covering owners, writers, readers, cutover, reconciliation, rollback, and acceptance. Use when decision owners need evidence to ratify or reject a migration contract; the skill cannot ratify it.
- ▌ Agent Protocol Interoperability Review · jovanipink bundleReview interoperability across agent, tool, and service protocols using exact versions, discovery records, schemas, identity, authorization, delegation, streaming, errors, retries, idempotency, cancellation, and trust zones. Use for A2A, MCP, or another agent-facing protocol boundary; use api-contract-compatibility-review for an ordinary API change without agent delegation semantics.
- ▌ Typescript Javascript Engineering Profile · jovanipink bundleApply focused TypeScript and JavaScript engineering judgment after repository gate discovery. Use for Node or browser packages, type safety, async behavior, tests, dependencies, compatibility, and builds; honor the repository package manager and scripts.
- ▌ Example Authority Policy · jovanipink bundleApply a fictional repository's local authority policy when reviewing example records. Use only inside this sanitized example to demonstrate private overlay placement.
- ▌ Task Handoff · jovanipink bundlePrepare a precise handoff for continuing work in another session, client, person, or agent using exact revisions, current state, evidence, decisions, blockers, and authority boundaries. Invoke explicitly when continuity matters and the recipient must not rediscover or overstate progress.
- ▌ Test Strategy · jovanipink bundleDesign risk-proportionate test coverage across unit, integration, contract, end-to-end, property, migration, and manual layers. Use when a feature, architecture change, or defect needs a justified coverage plan rather than only running existing checks.
- ▌ Plan Execution · jovanipink bundleExecute a named, approved implementation plan with checkpoints, validation, deviation tracking, and strict stopping boundaries. Invoke explicitly when the user authorizes implementation against an identified plan.
- ▌ Problem Framing · jovanipink bundleFrame a proposed feature, defect, workflow, or system change before implementation by identifying users, outcomes, evidence, constraints, unknowns, options, and measurable success. Use when a request is important but the problem or desired result is not yet decision-ready.
- ▌ Prototype Spike · jovanipink bundleRun a bounded prototype or technical spike to answer a named uncertainty with disposable or isolated work and explicit evidence. Invoke explicitly when the user authorizes implementation for learning but has not authorized production adoption, merge, or release.
- ▌ Claim Verification · jovanipink bundleVerify claims that work is complete, broken, missing, merged, deployed, or live by checking the relevant repository and platform evidence. Use when a review, handoff, PR, agent, or collaborator makes claims that would materially change the next action.
- ▌ Code Change Review · jovanipink bundleReview an exact code change for correctness, regressions, security, compatibility, test quality, and maintainability using the diff and repository evidence. Use before commit, pull request, merge, or release when the user wants findings rather than implementation.
- ▌ Test Driven Change · jovanipink bundleGuide feature and defect work through red, green, and refactor evidence while preserving a clear exception path when test-first work is unsuitable. Use for behavior changes where an executable test can prove the defect or desired outcome before implementation.
- ▌ Worktree Isolation · jovanipink bundleAssess whether dirty or concurrent repository work needs Git worktree isolation and design a safe isolation approach. Use when work may overlap existing changes; require explicit authority before creating, moving, locking, repairing, or removing a worktree.
- ▌ Alignment Interview · jovanipink bundleEstablish a shared, decision-ready understanding before implementation by inspecting available evidence and asking one material question at a time. Use when goals, constraints, terminology, or success criteria are unclear; do not use to delay an already approved and sufficiently specified change.
- ▌ Prelaunch Readiness · jovanipink bundleAudit whether a web property, service, application, or major relaunch is ready for public use, separating repository checks from provider and live-runtime evidence. Use for launch checklists, release readiness, and go or no-go reviews.
- ▌ Request Code Review · jovanipink bundlePrepare an evidence-bounded code review packet and, only when separately authorized, send or publish the request. Invoke explicitly when a change is ready for reviewer attention and its scope, checks, risks, and unresolved decisions must be stated precisely.
- ▌ Test Quality Review · jovanipink bundleReview the quality of a test suite or change-specific tests for meaningful assertions, defect sensitivity, isolation, determinism, risk coverage, and maintenance cost. Use when existing gates pass but the strength of the tests themselves is uncertain.
- ▌ Accessibility Review · jovanipink bundleReview web or application accessibility using WCAG 2.2 success criteria, semantic structure, keyboard behavior, assistive-technology needs, visual presentation, and user impact. Use for evidence-based findings without claiming conformance from incomplete testing.
- ▌ Codebase Explanation · jovanipink bundleExplain how an existing codebase works using current repository evidence: entrypoints, ownership, control and data flow, state, interfaces, failures, and concrete files. Use when the user asks how code behaves; use design-rationale-investigation instead for historical intent or why a design was chosen.
- ▌ Guided Configuration · jovanipink bundleGuide a person through configuration steps that require their account, device, approval, credential, or external interface while verifying each observable result. Invoke explicitly when the agent cannot or should not perform the protected step itself.
- ▌ Observability Design · jovanipink bundleReview or design observability for services and applications using logs, metrics, traces, alerts, and user-impact signals. Use when operators need to detect, explain, and respond to failures without confusing telemetry volume with operational understanding.
- ▌ Systematic Diagnosis · jovanipink bundleDiagnose a defect, failure, regression, or confusing behavior by reproducing it, narrowing the causal boundary, and reporting evidence. Use when the user asks why something fails or requests diagnosis without necessarily authorizing a fix.
- ▌ Publish Change Safely · jovanipink bundlePublish an authorized repository change by verifying identity, remote, branch, diff scope, checks, commit, push, PR state, and repository visibility. Use only when the user explicitly asks to commit, push, publish, or open a pull request.
- ▌ Skill Security Review · jovanipink bundleAudit an agent skill or plugin for prompt manipulation, unsafe commands, file and network blast radius, dependencies, hooks, permissions, data exposure, and deceptive behavior. Use before installing, promoting, or updating third-party or high-impact skills.
- ▌ Change Impact Analysis · jovanipink bundleAnalyze the blast radius of a proposed or completed change across callers, contracts, storage, jobs, clients, security, rollout, and operations. Use before review, merge, or release when downstream effects may be missed; do not substitute speculation for traced dependencies.
- ▌ Go Engineering Profile · jovanipink bundleApply focused Go engineering judgment after repository gate discovery. Use for Go modules, packages, concurrency, APIs, tests, dependencies, compatibility, and build concerns; defer exact commands to repository evidence.
- ▌ Requirements Synthesis · jovanipink bundleSynthesize interviews, documents, issues, observations, and constraints into traceable requirements. Use when multiple sources must become a decision-ready scope without turning proposals or preferences into ratified facts.
- ▌ Respond To Code Review · jovanipink bundleEvaluate code review feedback against current code, tests, contracts, and authority before accepting, rejecting, or deferring it. Use when review comments contain claims or requested changes that require technical verification.