backpack-code-review-checklist
openbooklet.com/s/backpack-code-review-checklistopenbooklet.com/s/backpack-code-review-checklist@1.0.0GET /api/v1/skills/backpack-code-review-checklistComprehensive code review checklist for Backpack design system components. Use when: (1) Reviewing PRs for new or modified Backpack components, (2) Validating component compliance with Constitution and design system rules, (3) Checking if component follows Backpack conventions before merge, (4) Identifying violations in API design, token usage, accessibility, or documentation. Covers Constitution principles (I-XIII), decisions/ guidelines, API encapsulation rules, private token restrictions, design approval workflow, icon alignment helpers, hover mixin usage, token semantic correctness, and snapshot currency. Essential for maintaining Backpack quality standards and catching non-obvious violations like className props in new components, wrong icon alignment wrapper, raw :hover instead of bpk-hover mixin, or cross-component private token usage.
This skill migrates a codebase from `@skyscanner/backpack-web` v41.x to v42.0.0. It handles all breaking changes introduced in the major version bump.
Migrate React components from external Skyscanner repositories (e.g., carhire-homepage) into Backpack design system components. Use when: (1) Component exists in app-specific repo with "unstable_backpack" or similar prefix, (2) Component needs to be promoted to official Backpack component, (3) Converting app code to follow Backpack constitution, (4) Extracting reusable UI patterns from product repos. Covers GitHub API access, Backpack naming conventions, modern Sass API, TypeScript patterns, license headers, accessibility testing, and Storybook integration. MANDATORY: Component must pass full test suite (npm run lint && npm run check-react-versions && npm run check-bpk-dependencies && npm run jest) with 0 errors before acceptance.
Auto-indexed from Skyscanner/backpack
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.