agustinusnathaniel-skills

Plugin agustinusnathaniel-skills from marketplace agustinusnathaniel-skills in agustinusnathaniel/skills. Commands read from the repo's manifest — yesterday.

Skills (19)

• autonomous-improvement-loop

  Compound small improvements on a recurring schedule without per-cycle direction. Use when running unattended improvement cycles over one repo or a portfolio.

• admin-panel-engineering

  Build or change admin panels, backoffice apps, and internal tools. Use when adding a permission-gated page, menu entry, route, or action; touching login, logout, session expiry, or role edits; scoping data to a tenant; or building filtered lists, exports, audit trails, destructive confirmations, ope

• bulk-import-engineering

  Build, fix, or audit data import and export: bulk file imports with validation previews, job status, and safe recovery; backup and restore; and JSON, CSV, or spreadsheet import and export, including in local-first apps. Excludes ordinary single-file uploads and file analysis.

• calculation-correctness

  Implement or review code that computes money, dates, units, counters, or derived metrics. Use for totals, fees, rounding, sequence numbers, timezone and day boundaries, unit conversion, aggregated charts, and edits that reconcile lists of rows that carry state.

• challenge-every-guard

  Size defensive code to evidence and fit a change to the codebase it lands in. Use when a change adds guards, retries, locks, fallbacks, validation, or new abstractions; when review rounds keep adding mechanism or a PR outgrows its feature; or when reviewing a backend change to services, jobs, events

• client-trust-boundary

  Decide what a web or mobile client may hold and what the server must enforce. Use when exposing environment variables or API keys to a client, calling a backend-as-a-service (Firebase, Supabase, Convex) from the client, gating features by role in the UI, storing sessions or roles on the device, or r

• codebase-dossier

  Write an evidence-cited dossier of a codebase or several related repos, covering purpose, architecture, operations, history, decisions, and sharp edges.

• config-drift

  Verify that a configuration change is what the running system actually uses. Use when changing environment variables, build-time config, security headers or CSP, service worker or update settings, hosting or platform config files, or agent and tool config, and when a setting has no effect or a featu

• expo-app-foundations

  Build or change the foundations of an Expo or React Native app. Use when setting up environments, release channels, or over-the-air updates; adding remote config, forced updates, or feature flags; handling token refresh, push notifications, or deep links; embedding web views; or adding native module

• github-actions-authoring

  Write or change GitHub Actions workflows. Use when adding CI jobs, caching, or timeouts; building a reusable workflow or composite action that other repos call; automating commits, releases, or dependency-update PRs; or debugging a workflow that passes without checking anything or behaves unlike its

• hydration-safe-state

  Keep hydration consistent when server-rendered or prerendered HTML meets browser-only state. Use when debugging hydration mismatches, a theme flash, or a page that differs between navigation and reload; or when adding a theme toggle, persisting state to localStorage or cookies, restoring an auth ses

• prune-codebase

  Use for substantial codebase pruning or removal of overengineering across production code and its tests, documentation, agent instructions, configuration, and tooling, including follow-up passes after a reduction PR. Not for ordinary feature work or minor cleanup.

• pull-request-readiness

  Get a pull request, or a stack of them, to mergeable. Use when splitting work into PRs or stacks, checking a PR is ready before marking it ready or requesting review, triaging bot and CI findings, or preparing the merge and deploy steps for the user.

• pull-request-review

  Review someone else's pull request and draft the comments the user posts under their name. Use when asked to review a PR, draft review comments, or reply in a review thread.

• react-app-structure

  Decide where code goes in a React web app (Vite with TanStack Router, or Next.js). Use when adding a page, route, feature, API call, or shared component, or when moving logic out of a component.

• test-strategy

  Choose what to test or verify for a change, and at which boundary. Use when reproducing a bug before fixing it, choosing unit, integration, or end-to-end coverage, judging whether existing tests earn their keep, or changing prompts, schemas, or model settings.

• tool-evaluation-and-adoption

  Vet an open-source tool, library, package, plugin, skill, or MCP server before adopting it. Use when asked whether to adopt, switch to, or upgrade one, to install one, or to triage dependency and supply-chain alerts.

• typescript-code-conventions

  Write TypeScript that fits the repository first and these conventions second, with or without a linter. Use when writing or changing TypeScript or TSX, or when a lint rule on function shape, errors, types, imports, exports, file names, or React components fails.

• url-state

  Put view state in the URL or read it back. Use when adding search params, filters, pagination, or sort to a URL; building shareable or deep links into lists; syncing a search box with the address bar; or when a shared link crashes, opens the wrong view, or leaks the sender's state.