.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/j-pster/psters_ai_workflow
home/skills/j-pster/psters_ai_workflow
j-pster avatar

j-pster/psters_ai_workflow

17 skills

View on GitHub
$npx skills add j-pster/psters_ai_workflow
SkillInstalls
angular-conventionsFrontend conventions for Angular projects: standalone components, features, error capture, styles. Use when implementing or reviewing code in Angular frontends.—commit-changesCommit uncommitted changes across all workspace repos and tag commits with ticket numbers.—commit-changes-repo-workerPer-repo commit worker. Analyzes ALL changed files independently, groups them by ticket, and makes MULTIPLE focused commits — one per logical group.—deploy-lambdaDeploy AWS Lambdas using the guaranteed deploy scripts only. Never deploy via IAC (CDK). Requires AWS SSO login first. Use when deploying any AWS Lambda repo.—docs-baseline-loadingLoad and enforce mandatory project documentation baseline before implementation work.—docs-maintenance-after-workRun standardized post-implementation documentation maintenance and quality checks.—finishing-a-development-branchUse when implementation is complete to close branch/worktree with a disciplined decision flow (merge, PR, keep, discard) plus cleanup.—git-worktreeManages Git worktrees for isolated parallel development. Use when creating separate working directories for branches without switching the main repo.—nestjs-conventionsBackend conventions for NestJS projects: modules, controllers, services, DTOs, migrations, structure.—orchestrating-multi-agentsUse for explicit multi-subagent orchestration when tasks are independent and parallelization improves quality or speed while preserving deterministic merge.—receiving-code-reviewUse when processing review feedback to prioritize critical findings and resolve comments safely before commit.—requesting-code-reviewUse when requesting a focused review with standardized findings format (critical, important, informational) before commit or PR.—systematic-debuggingUse for bugs, failing tests, and unexpected behavior; enforce a 4-phase root-cause-first debugging process before implementing fixes.—test-driven-developmentOptional TDD workflow; use only when user explicitly requests TDD/tests (red-green-refactor with minimal scope).—using-psters-workflowMeta-skill for selecting and invoking the right workflow skill before acting; use when starting or switching task type to avoid bypassing required discipline.—verification-before-completionUse before any completion/success claim to enforce fresh verification evidence (build/lint/tests/repro command) and explicit limitations when verification is…—visual-brainstorm-companionUse during brainstorm only when the problem is strongly visual (complex UI, flow mapping, alternatives) and create optional browser/canvas artifacts.—