bonnguyenitc

@bonnguyenitc source repo

32 skills
0 followers
1 day ago last updated

▌
Ss Plan · bonnguyenitc bundle
Design an implementation plan from a confirmed spec before writing code. Use after the spec is confirmed, when asked to "plan this feature", "how should we implement X", "break this down into steps", or "lên kế hoạch". Produces an ordered, verifiable step-by-step plan with files to touch, approach, tradeoffs, and per-step success checks. Second stage of the specship pipeline.

0
installs
▌
Ss Ship · bonnguyenitc bundle
Take a feature request from idea to reviewed, ready-to-commit code in one run — spec → plan → coding → review (+ debug on defects) — without asking at each stage. Use when given a request like "/ss-ship implement login", "ship this feature", "do the whole flow for X", "làm hết flow cho chức năng X". Orchestrator over the stage skills; never runs ss-explore-source.

0
installs
▌
Ss Spec · bonnguyenitc bundle
Read and fully understand a spec, ticket, PRD, or feature request before any planning or coding. Use when given requirements to implement, when asked to "understand this spec", "what does this ticket mean", or as the first step of a feature. Extracts goals, requirements, acceptance criteria, edge cases, and open questions. First stage of the specship pipeline.

0
installs
▌
Ss Debug · bonnguyenitc bundle
Diagnose and fix a bug methodically, and track the investigation in the owning task. Use when something is broken, a test fails, behavior is wrong, or asked to "debug X", "fix this bug", "why is this failing". Reproduces, finds root cause, fixes minimally, verifies, and records it in tasks/TASK-<ID>/debug.md. Attaches to the spec → plan → coding → review workflow whenever a defect appears.

0
installs
▌
Ss Coding · bonnguyenitc bundle
Implement an approved plan step by step, following the project's conventions, and verify each step. Use after a plan exists, when asked to "implement this", "code it up", "build the feature", or "code đi". Writes minimal, surgical code matching existing style and runs each success check before starting the next step. Third stage of the specship pipeline.

0
installs
▌
Ss Review · bonnguyenitc bundle
Wrap up a finished change — self-review the diff, run the full test/lint gate, verify against acceptance criteria, update docs, then prepare commit/PR. Use after coding is done, when asked to "review my changes", "wrap up", "finalize", or "is this ready to merge". Final stage of the specship pipeline.

0
installs
▌
Ss Research · bonnguyenitc bundle
Research a topic, technology, library, or decision using the strongest search tool available in the session. Use when asked to "research X", "compare X vs Y", "find the best library/tool for X", "what's the latest on X", "how does <external service or API> work", or whenever an answer depends on external facts (versions, APIs, pricing, benchmarks, best practices) that must be current and cited rather than recalled from memory. Prefers specialized MCP search tools over generic web search and always ends by producing a complete, verified, cited research report.

0
installs
▌
Ss Pause Task · bonnguyenitc bundle
Deliberately set an in-progress task aside to pick up later — mark it paused with a reason, leaving every pipeline artifact untouched. Use when work halts by choice rather than by a blocker, or when asked to "pause", "park", "hold this task", "tạm dừng task", "để task này lại sau". The inverse of ss-resume-task; changes status, not progress.

0
installs
▌
Ss Resume Task · bonnguyenitc bundle
Pick up an in-progress task exactly where it was left off — locate it, report where it stands, and continue from the current stage. Use when returning after a break or context reset, or when asked to "resume", "continue the task", "pick up where we left off", "tiếp tục task", "đang làm tới đâu rồi". Entry point over the stage skills; the interactive counterpart to ss-ship.

0
installs
▌
Ss Archive Task · bonnguyenitc bundle
Retire a finished or abandoned task by relocating its whole folder into tasks/archive/, history preserved, so scans over the active set skip it. Use for a task that is finished or has been abandoned, or when asked to "archive", "shelve", "put this task away", "lưu trữ task", "dọn task xong". Reversible via ss-resume-task. Lifecycle skill, not a stage.

0
installs
▌
Ss Explore Source · bonnguyenitc bundle
Explore and explain an unfamiliar codebase for onboarding. Use when a developer joins a project, when asked to "understand the codebase", "explain the architecture", "how does this project work", "where is X handled", or before making changes in code you haven't seen yet. Produces a structured map of stack, architecture, entry points, conventions, and how to run/test.

0
installs
▌
Copywriter · bonnguyenitc
Use when writing landing page copy, app store descriptions, onboarding flows, email sequences, push notifications, or any user-facing text

0
installs
▌
UX Designer · bonnguyenitc
Use when designing UI, creating wireframes, running user research, defining information architecture, or reviewing design decisions — regardless of tool (Figma, Sketch, etc.)

0
installs
▌
Brainstorming · bonnguyenitc bundle
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

0
installs
▌
Writing Plans · bonnguyenitc bundle
Use when you have a spec or requirements for a multi-step task, before touching code

0
installs
▌
Writing Skills · bonnguyenitc bundle
Use when creating new skills, editing existing skills, or verifying skills work before deployment

0
installs
▌
Executing Plans · bonnguyenitc
Use when you have a written implementation plan to execute in a separate session with review checkpoints

0
installs
▌
Frontend Design · bonnguyenitc bundle
Use when building web components, pages, artifacts, or applications — especially when high design quality is needed. Generates creative, polished code that avoids generic AI aesthetics (purple gradients, Inter font, card-in-card layouts).

0
installs
▌
Product Manager · bonnguyenitc
Use when defining product requirements, prioritizing features, planning a roadmap, validating user problems, or making build/buy/don't-build decisions

0
installs
▌
Mobile Developer · bonnguyenitc bundle
Use when working on mobile app features, reviewing mobile code, or making architecture decisions — regardless of platform (React Native, Flutter, iOS, Android)

0
installs
▌
I18N Localization · bonnguyenitc
Use when planning internationalization (i18n) architecture, localizing an app for new markets, managing translations, or optimizing for non-English app store listings

0
installs
▌
Using Superpowers · bonnguyenitc bundle
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

0
installs
▌
Frontend Developer · bonnguyenitc bundle
Use when building web UI, designing component architecture, or reviewing frontend code — regardless of framework (React, Vue, Svelte, etc.)

0
installs
▌
Mobile Uiux Promax · bonnguyenitc
Use when designing or building mobile app UI for iOS, Android, React Native, Flutter, SwiftUI, or Jetpack Compose

0
installs
▌
Using Git Worktrees · bonnguyenitc
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

0
installs
▌
Subscription Billing · bonnguyenitc
Use when integrating subscription billing, handling Stripe webhooks, implementing trial logic, managing upgrades/downgrades, or building dunning flows

0
installs
▌
Systematic Debugging · bonnguyenitc bundle
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

0
installs
▌
Test Driven Development · bonnguyenitc bundle
Use when implementing any feature or bugfix, before writing implementation code

0
installs
▌
Dispatching Parallel Agents · bonnguyenitc
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

0
installs
▌
Subagent Driven Development · bonnguyenitc bundle
Use when executing implementation plans with independent tasks in the current session

0
installs
▌
Finishing A Development Branch · bonnguyenitc
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

0
installs
▌
Verification Before Completion · bonnguyenitc
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

0
installs

32 published skills