All authors
Claude Skills by HoangNguyen0403
github.com/HoangNguyen04031,434 skills30 installs1,975 views
- Common Subagent Driven DevelopmentExecute multi-task implementation plans by dispatching a fresh implementer subagent per task with independent review gates. Use when implementing plans, executing multi-task PRs, or transitioning from planning to implementation.Votes: 0GitHub stars: 571
- Cyber Framework MappingMaintains sparse, reviewable cybersecurity framework edges with versioned IDs, relation, rationale, source, and review status. Use when mapping exercise observations or procedures to NIST, ATT&CK, or another named framework.Votes: 0GitHub stars: 571
- Common Decision DisciplineRight-size, ground, and gate SDLC decisions with SNC-sized depth, said-vs-assumed write-back, an evidence ledger, honest option cards, recorded approval, and self-review. Use when running brainstorm-feature, plan-feature, design-solution, or system-design-session.Votes: 0GitHub stars: 571
- Common Task Complexity RoutingScores a coding task on Spread, Novelty, and Centrality (SNC 0-6) and maps the tier to autonomy, verification depth, review mode, reviewers, model tier. Use when sizing a fix or feature before planning, choosing fast vs deep review, or deciding whether HARD STOP approval is required.Votes: 0GitHub stars: 565
- Quality Engineering Automation HealthMeasures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a release_confidence verdict. Use when judging suite value, ROI, or pre-release trust; not for writing or healing tests.Votes: 0GitHub stars: 565
- Quality Engineering Flaky TriageQuarantines an intermittently failing test behind a ticket with an owner and expiry, assigns a root-cause bucket from isolated reruns, and defines when the test leaves quarantine. Use when a test is a QUARANTINE_CANDIDATE or fails without a code change; not for deterministic failures.Votes: 0GitHub stars: 565
- Quality Engineering Playwright Pom GenerationGenerates Playwright page objects from an executable test plan, one class per screen with ladder-compliant locators and no assertions, wired into a shared fixture. Use when a web scenario needs a page object that does not exist yet, or when locators drift and the page object must be rebuilt.Votes: 0GitHub stars: 565
- Quality Engineering Selector StabilityCross-stack selector and test-id policy for web and mobile automation. Use when writing or reviewing E2E/UI test locators, or adding data-testid/accessibility identifiers to components.Votes: 0GitHub stars: 565
- Quality Engineering Test HealingFailure taxonomy and allowed/forbidden repairs for a failing E2E test. Use when a Playwright/Maestro/Detox/XCUITest/Espresso/Appium test fails and you must decide whether to repair the test or route to a real bug.Votes: 0GitHub stars: 565
- Quality Engineering Test Plan AuthoringTurn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code. Use when ACs exist but no runnable test plan does yet.Votes: 0GitHub stars: 565
- Quality Engineering Visual BaselineCaptures, masks, compares, and updates screenshot baselines for web and mobile suites, with per-region thresholds and a reviewed-diff rule for every baseline change. Use when a screenshot assertion fails, a baseline needs updating, or visual checks are being added; not for deciding what to verify.Votes: 0GitHub stars: 565
- System Design Interview CoachingRuns a timed mock system design round as the interviewer, then scores it as the coach: seven phases on a 45-minute clock, one follow-up on the weakest area, Mermaid sketches in chat, a six-criterion 0-3 rubric with quoted evidence. Use for interview practice, prep, or grading a practice design.Votes: 0GitHub stars: 565
- Test LoopPlan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).Votes: 0GitHub stars: 565
- Javascript LanguageModern JavaScript (ES2022+) patterns for clean, maintainable code. Use when working with modern JavaScript features like optional chaining, nullish coalescing, or ESM.Votes: 0GitHub stars: 565
- Specialist Solution DiagrammerDraws one evidence-grounded architecture diagram as an editable draw.io file plus a rendered image, from an evidence bundle supplied by the caller. Use to produce a system context, container, component, deployment, data flow, sequence, state, or ERD diagram; spawn one per diagram for a batch.Votes: 0GitHub stars: 565
- Specialist Test HealerClassifies one failing E2E test from its artifacts, applies at most one allowed repair from the test-healing catalog, proves it with three sequential reruns and an unchanged assertion set, and returns a verdict with a route. Use per failure inside test-loop; never for production code changes.Votes: 0GitHub stars: 565
- Specialist Test PlannerTurns approved AC/SRS into an executable test plan (scenarios, seed, selector gaps) for the test-loop workflow. Use for independent test-plan generation from stable requirements.Votes: 0GitHub stars: 565
- Specialist Testid InserterInserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.Votes: 0GitHub stars: 565
- Common Workflow WritingRules for writing concise, token-efficient workflow and skill files. Prevents over-building that requires costly optimization passes. Use when creating or editing workflow files, SKILL.md files, or new skill definitions.Votes: 0GitHub stars: 549
- Deploy ReleasePrepare and verify a staged or production deployment with rollback and smoke checks.Votes: 0GitHub stars: 549
- Design SolutionTurn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.Votes: 0GitHub stars: 549
- Dev FixUnified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.Votes: 0GitHub stars: 549
- Implement FeatureImplement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.Votes: 0GitHub stars: 549
- Implementation ReadinessVerify BRD-lite, PRD, SRS/FRS, UX, and test prerequisites before implementation starts.Votes: 0GitHub stars: 549
- PentestPTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.Votes: 1GitHub stars: 549
- Plan FeaturePlan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.Votes: 0GitHub stars: 549
- Publish NotesDraft user-facing release notes, store changelogs, and internal publish summaries.Votes: 0GitHub stars: 549
- Quality Engineering Appium McpDrives iOS/Android mobile devices via Appium MCP. Runs a preflight, picks local emulator/simulator/USB or a device cloud, captures screenshots/page source into a named evidence dir. Use for verifying mobile bugs, E2E tests, and navigating real device clouds (LambdaTest/BrowserStack).Votes: 0GitHub stars: 549
- Quality Engineering Business AnalysisInvestigate requirements with atomic AC decomposition, actor/permission matrix, platform parity audit, truth table verification, and edge case discovery. Also enforces User Story authoring standards: story structure, scope fences, platform tags, toggle contracts, market isolation, and deferral patterns. Use when writing, reviewing, or improving User Stories, acceptance criteria, or doing impact analysis — especially for stories with multi-condition AC, feature toggles, market variants (VN/MY/...Votes: 0GitHub stars: 549
- Quality Engineering Jira IntegrationJira ↔ Zephyr traceability: fetch story AC and components, detect existing TC links, link new Zephyr TCs back to Jira, and apply has-zephyr-tests labels. Use after creating Zephyr test cases that need linking, when fetching a Jira story's details for test generation, or when auditing and cleaning up stale TC links.Votes: 0GitHub stars: 549
- Quality Engineering Playwright CliStandardizes token-efficient browser automation via playwright-cli, with Playwright MCP as the fallback driver. Runs a preflight, picks the driver rung, captures aria snapshots/console/screenshots into a named evidence dir. Use for web verification, navigation, and capturing snapshots/logs.Votes: 0GitHub stars: 549
- Quality Engineering Quality AssuranceWrite manual test cases with 1-condition-per-TC granularity, Module_Action on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use when writing or reviewing manual test cases for Zephyr — to split compound TCs, fix naming violations, assign correct platform tags, or determine bug priority.Votes: 0GitHub stars: 549
- Quality Engineering Zephyr Coverage AnalysisAudit test coverage health, gaps, and QE debt for Jira stories or epics. Produces coverage_analysis_report.md with AC-to-TC heatmap, risk scores, and prioritized action plan. Use when assessing coverage percentage, pre-release readiness, sprint readiness, or identifying missing test cases. Do NOT use for TC creation — use zephyr-test-generation instead.Votes: 0GitHub stars: 549
- Quality Engineering Zephyr Test GenerationGenerate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.Votes: 0GitHub stars: 549
- Retro LearnConvert delivery findings into skill, eval, workflow, and documentation improvements.Votes: 0GitHub stars: 549
- Review TicketReview a ticket or PR through focused specialist lenses: scope, architecture, security, tests, AC coverage, and PR metadata.Votes: 0GitHub stars: 549
- SdlcRoute a task to the next synced SDLC workflow based on current artifacts and repo state.Votes: 0GitHub stars: 549
- Security TestFast, continuous DevSecOps pipeline for Pull Requests and active branches. Runs SAST, SCA, and secrets detection to catch vulnerabilities before they merge.Votes: 0GitHub stars: 549
- Session ReportCapture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.Votes: 0GitHub stars: 549
- Skill BenchmarkBenchmark AI skill effectiveness by measuring implementation quality against legacy constraints.Votes: 0GitHub stars: 549
- Traceability AuditMap requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.Votes: 0GitHub stars: 549
- Typescript Best PracticesWrite idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic.Votes: 0GitHub stars: 549
- Typescript LanguageApply modern TypeScript standards for type safety and maintainability. Use when working with types, interfaces, generics, enums, unions, or tsconfig settings.Votes: 0GitHub stars: 549
- Typescript SecurityValidate input, secure auth tokens, and prevent injection attacks in TypeScript. Use when validating input, handling auth tokens, sanitizing data, or managing secrets and sensitive configuration.Votes: 0GitHub stars: 549
- Typescript ToolingDevelopment tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.Votes: 0GitHub stars: 549
- Update DocsAutomated workflow to detect and fix missing documentationVotes: 0GitHub stars: 549
- Verify BugPost-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.Votes: 0GitHub stars: 549
- Verify WorkVerify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.Votes: 0GitHub stars: 549
- Zephyr Coverage AnalysisAnalyze Zephyr test case coverage for a Jira user story and produce a QE management report with metrics, risk scoring, and prioritized recommendations.Votes: 0GitHub stars: 549
- Common Best PracticesEnforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity.Votes: 0GitHub stars: 549