All authors
Claude Skills by jrodrigopuca
github.com/jrodrigopuca48 skills0 installs0 views
- Code ReviewReviewing Swift/SwiftUI code as mentor: the severity system, the Apple-specific defect checklist, and review-as-teaching. Trigger: load when the user shares Swift, SwiftUI, UIKit, or AppKit code for review, feedback, or "is this okay?".Votes: 0GitHub stars: 2
- DebuggingDebugging Apple-platform issues as taught method: crashes, leaks, hangs, and weird behavior — Socratic first, tools named, root cause always. Trigger: load on crashes, memory leaks, hangs, "it behaves weird", or any "why is this happening?" in Swift/iOS/macOS.Votes: 0GitHub stars: 2
- ShippingGetting apps into users' hands: signing, provisioning, TestFlight, App Review, and macOS-specific distribution (notarization, outside-MAS). Trigger: load on anything involving certificates, provisioning profiles, TestFlight, App Store Connect, App Review, entitlements, or distributing a Mac app.Votes: 0GitHub stars: 2
- State ArchitectureSwiftUI state management and app architecture: ownership, MVVM shape, navigation, dependency injection, project structure, concurrency placement. Trigger: load on questions about state ("why doesn't my view update?"), architecture, where code should live, WHERE CODE RUNS (main actor, background, "does async mean another thread?"), or how to structure a new feature/project. Answer concurrency from this skill before the web: it carries the Xcode 26 isolation defaults.Votes: 0GitHub stars: 2
- Design ReviewHow to review a codebase's architecture or a proposed design: dependency direction, boundary integrity, coupling smells, severity calibration. Trigger: load when asked to review architecture, evaluate a codebase's structure, assess a design doc, or when a PR changes module boundaries.Votes: 0GitHub stars: 2
- MentoringThe teaching model: how to turn a correction into learning without becoming an interrogator. Trigger: load when the escalation ladder fires a teachable moment — a real misconception, skipped fundamentals, or an expensive decision being made casually.Votes: 0GitHub stars: 2
- TradeoffsMethod for analyzing and presenting expensive-to-reverse technical decisions: drivers, options, tradeoff table, recommendation, ADR shape. Trigger: load when a decision is costly to change later (data model, service boundaries, framework, sync/async, build-vs-buy), when the user asks "should we use X or Y", or when a project decision needs recording or an existing one is being reopened.Votes: 0GitHub stars: 2
- Data PipelinesMoving data reliably: ingestion, transformation, quality validation, storage, and pipeline design. Trigger: load when building or fixing data pipelines, ETL/ELT, data quality issues, or deciding how to store and model DERIVED data (warehouse, lake, feature store) — the transactional source of truth is dba's.Votes: 0GitHub stars: 2
- Llm IntegrationBuilding reliable product features on LLMs: RAG, prompting-as-code, output validation, evals, and cost/latency engineering. Trigger: load when integrating an LLM into a product — chat, extraction, RAG, agents, or any "add AI to this" request.Votes: 0GitHub stars: 2
- Ml ModelingFraming and building ML solutions honestly: problem framing, baselines, evaluation, and deployment. Trigger: load when framing an ML problem, choosing/training a model, designing evaluation, or deploying a model to production.Votes: 0GitHub stars: 2
- Data ModelingDesigning schemas that survive real data: entities, keys, constraints, normalization and when to break it, and modelling access alongside structure. Trigger: load when designing a new schema, reviewing a proposed table or ORM model, or when an existing model keeps producing awkward queries.Votes: 0GitHub stars: 2
- MigrationsChanging a schema that already holds real data: expand/contract, reversible steps, backfills that don't lock, and stating what a deploy strategy must respect. Trigger: load when altering an existing table, renaming or dropping anything, backfilling data, or when a release couples code to a schema change.Votes: 0GitHub stars: 2
- Query PerformanceMaking reads cheap by design: execution plans, index strategy, N+1 detection, and diagnosing slowness against real cardinality instead of guessing. Trigger: load when a query or page is slow, when designing the access paths a feature needs, or when deciding whether an index is worth its cost.Votes: 0GitHub stars: 2
- Ci CdBuild/test/deploy pipelines and release strategies: automation, stages, deployment patterns (blue-green, canary, rolling), and reversibility. Trigger: load when setting up or fixing CI/CD, choosing a deploy strategy, or when releases are painful, manual, or risky.Votes: 0GitHub stars: 2
- InfrastructureInfrastructure as code, containers, environments, cloud, secrets, and scaling: building reproducible systems from zero. Trigger: load when provisioning infra, containerizing, managing environments/secrets, or making scaling/cost decisions.Votes: 0GitHub stars: 2
- ObservabilityKnowing what production is doing: logs, metrics, traces, meaningful alerts, and SLOs. Trigger: load when adding monitoring, designing alerts, debugging a production issue blind, or defining what "healthy" means for a service.Votes: 0GitHub stars: 2
- DeliveryGetting work delivered predictably: planning, estimation, scoping, tracking, and de-risking. Trigger: load when planning work, estimating, breaking down an epic, tracking progress, or a project is slipping/at risk.Votes: 0GitHub stars: 2
- OrchestrationRouting work across the agent team and composing multiple agents on shared tasks: the roster map, routing heuristics, and handoff choreography. Trigger: load when a task spans multiple specialties, when unsure which agent fits, or when coordinating several agents on one piece of work.Votes: 0GitHub stars: 2
- Team HealthKeeping the team (of agents and people) effective and sustainable: minimal process, retrospectives, unblocking, and continuous improvement. Trigger: load when designing/adjusting process, running a retro, addressing recurring friction, or when the team's way of working needs tuning.Votes: 0GitHub stars: 2
- EngagementAttracting users and bringing them back: onboarding as a game's first session, habit loops, return triggers, and honest engagement metrics. Trigger: load when working on onboarding, activation, retention, churn, or when asked "how do we get users to come back / stick around".Votes: 0GitHub stars: 2
- Flow AnalysisHow to walk a product flow as an analyst: map it from the user's side, audit friction and motivation step by step, and simplify before gamifying. Trigger: load when asked to analyze, review, or improve any user flow, funnel, or journey — always BEFORE proposing mechanics.Votes: 0GitHub stars: 2
- Game MechanicsThe gamification toolbox with judgment: core loops, progression, rewards, social mechanics — what each one does, whom it serves, and its shadow side. Trigger: load when choosing, designing, or tuning game mechanics for a product flow (only after flow-analysis has run).Votes: 0GitHub stars: 2
- DecompositionHow to break non-trivial work into independently verifiable steps ordered by uncertainty reduction. Trigger: load before planning any task that needs more than one action, spans multiple files, or contains an assumption you haven't confirmed.Votes: 0GitHub stars: 2
- Next StepDecision model for choosing what to do next: continue, re-plan, stop, or escalate to the user. Trigger: load after a step fails or surprises you, before ending a turn on a task that took more than one step, before starting a task of more than a handful of steps, or when resuming one ("seguimos con lo de ayer"). Not needed when the next action is obvious and reversible.Votes: 0GitHub stars: 2
- VerificationHabits for proving claims before making them: the evidence ladder, when to verify, and how to phrase confidence honestly. Trigger: load before claiming done on work with a runtime surface, before building on a technical assertion you have not checked, and before fixing a bug you have not reproduced. Not needed for a one-line factual answer — the base context covers that.Votes: 0GitHub stars: 2
- BacklogTurning validated problems into buildable work: user stories, acceptance criteria, prioritization, and roadmap. Trigger: load when writing requirements/stories, prioritizing a backlog, planning a roadmap, or defining what "done" means for a product change.Votes: 0GitHub stars: 2
- DiscoveryValidating that a problem is real and worth solving before anyone builds: user research, assumption-testing, and opportunity assessment. Trigger: load when evaluating a new feature/idea, deciding whether to build something, or when a request arrives as a solution and the problem is unclear.Votes: 0GitHub stars: 2
- StakeholdersAlignment and communication: managing stakeholders, communicating product decisions, saying no gracefully, and setting expectations. Trigger: load when aligning stakeholders, communicating a decision or roadmap, handling a pushed-in request, or managing expectations up and across.Votes: 0GitHub stars: 2
- Bug ReportingTurning findings into action: minimal reproductions, severity honesty, and the collaboration loop with dev and ux-ui. Trigger: load when reporting a found issue, triaging findings, verifying a fix, or deciding whether something is a bug, a design gap, or an improvement.Votes: 0GitHub stars: 2
- Flow HuntingSystematic hunting of unconsidered paths: edge cases, interruptions, state collisions, and hostile inputs. Trigger: load when exploring a feature or flow for potential bugs, reviewing a spec for gaps, or asked "what could break here?".Votes: 0GitHub stars: 2
- Test DesignJudgment for writing and reviewing test code: what to test at which level, how to keep tests trustworthy, and how to audit an existing suite. Trigger: load when writing test code, reviewing a test suite, or deciding what automated coverage a feature needs.Votes: 0GitHub stars: 2
- Code AuditExhaustive code auditing for vulnerability classes: injection, authz, auth, secrets, crypto, deps, and the method for reading code adversarially. Trigger: load when auditing code for security flaws, reviewing a diff for vulnerabilities, or hunting a specific vuln class.Votes: 0GitHub stars: 2
- RemediationTurning security findings into fixes: the actionable report, severity ranking, fix-the-class prescriptions, and verification. Trigger: load when reporting vulnerabilities, prioritizing a findings list, prescribing fixes, or verifying a security fix.Votes: 0GitHub stars: 2
- Threat ModelingMapping attack surface and trust boundaries before reading code: entry points, data flows, trust zones, and adversary goals. Trigger: load when starting a security assessment, designing a feature securely, or asked "what could an attacker do here / where are we exposed?".Votes: 0GitHub stars: 2
- Code HealthClean code judgment and technical debt management: what to improve while touching code, when to take debt consciously, and which debt to pay first. Trigger: load when deciding whether an improvement belongs in this diff or in a ticket, when tempted to take a shortcut, or when choosing which debt to pay first. The clean-code baseline is always on and needs no skill.Votes: 0GitHub stars: 2
- Fullstack BoundariesJudgment for work that crosses the wire, in any stack: API contracts, runtime validation at edges, where logic lives, errors end-to-end. Trigger: load when work crosses the wire — designing/consuming APIs, handling forms, touching the data layer, or wiring frontend to backend.Votes: 0GitHub stars: 2
- PairingHow to work as a peer: reviewing a teammate's code, debugging together, and splitting work. Trigger: load when reviewing the user's code as a colleague, co-debugging an issue, or dividing a task between you and the user.Votes: 0GitHub stars: 2
- React NextDecision criteria for React/Next.js feature work: server/client split, state placement, component boundaries, data flow. Trigger: load when building or restructuring React components, pages, or data fetching in a React app. The server/client and data-fetching patterns apply to Next.js App Router (or a framework with server rendering and loaders); a Vite SPA or React Native takes the state ladder and the boundaries and skips those. Complements (does not replace) any `react-19` / `nextjs-*` ski...Votes: 0GitHub stars: 2
- Crisis ModeOperating under fire: production incidents, deadline collapses, demo-eve disasters. Stabilize, diagnose, fix, learn — in that order, with a cool head. Trigger: load when something is broken NOW and the cost of downtime is running — outages, data issues, launch-day failures, demo-tomorrow panics.Votes: 0GitHub stars: 2
- First PrinciplesAttacking complex or stuck problems: decomposition to fundamentals, reframing, cross-domain theft, and unsticking heuristics. Trigger: load when a problem is complex, ambiguous, or stuck — when the obvious approaches failed or nobody knows where to start.Votes: 0GitHub stars: 2
- Zero To OneTaking a product from nothing to shipped v1: phase rules, riskiest assumption first, walking skeletons, and honest prototype-to-production transitions. Trigger: load when starting a product from scratch (greenfield: nothing exists yet), planning an MVP, or when a prototype is being promoted to production. A new feature inside an existing codebase is senior-dev's, not this.Votes: 0GitHub stars: 2
- Dev HandoffTranslating design into implementable specs: design-tool-to-code concept mapping, design tokens, component specs, UI acceptance criteria. Trigger: load when handing a design to a developer, discussing a Figma or Sketch file, defining tokens, or writing what "done" means for a UI task.Votes: 0GitHub stars: 2
- MockupsHow this agent actually produces design deliverables: the fidelity ladder from ASCII wireframe to HTML/CSS mockup to clickable prototype. Trigger: load when asked to design, mock up, wireframe, or prototype any screen or flow — before producing anything visual.Votes: 0GitHub stars: 2
- Ux FlowsJudgment for what the interface DOES: task flows, navigation, forms, states, and friction. Trigger: load when designing a user flow, a form, navigation structure, or when deciding how a feature behaves (not how it looks).Votes: 0GitHub stars: 2
- Visual CraftScreen-level visual judgment: hierarchy, spacing, typography, color, layout. Trigger: load when deciding how a screen or component looks — choosing sizes, spacing, type, colors — or when a screen "feels off" and needs diagnosis.Votes: 0GitHub stars: 2
- Brutal CritiqueHow to analyze a product and deliver a brutally honest verdict that raises the work without wounding the person. Trigger: load when asked to review, critique, or give an opinion on a product, feature, demo, pitch, or roadmap.Votes: 0GitHub stars: 2
- FocusThe discipline of saying no: killing features, cutting product lines, finding the one thing, and shipping with practical sense. Trigger: load when a roadmap is bloated, priorities are "everything", a feature list needs cutting, or scope and dates collide.Votes: 0GitHub stars: 2
- InspireMotivating toward creation: vision framing, benefit storytelling, and teaching through product history's real lessons. Trigger: load when the user needs momentum, direction, or conviction — starting something, stuck in the middle, doubting after a failure, or pitching a vision to others.Votes: 0GitHub stars: 2