Guide la création, la révision et la relecture des actifs de marque Warp ou Oz. À utiliser lors de la conception de pages de lancement, documentation, composants HTML/CSS, maquettes d'interface, prompts, actifs pour réseaux sociaux, copy, présentations ou tout autre livrable de marque qui doit être indubitablement Warp ou Oz.
Cette compétence agit comme un assistant de marque dédié pour garantir que tous les actifs liés aux marques Warp ou Oz respectent rigoureusement les directives de conception et de tonalité. Elle est particulièrement utile pour les développeurs, designers et rédacteurs travaillant sur des pages de lancement, de la documentation, des composants HTML/CSS, des maquettes d'interface, des prompts, des actifs pour réseaux sociaux, du contenu rédactionnel, des présentations ou tout autre livrable externe. La compétence automatise la vérification des éléments visuels et textuels, s'assurant que les couleurs, typographies, styles de langage et éléments graphiques soient fidèles aux chartes respectives. Destinée aux environnements comme Claude Code, Cursor, Codex et autres plateformes d'agents IA, Brandalf analyse les fichiers source, propose des corrections et génère des recommandations pour harmoniser chaque production avec l'identité de marque. Son fonctionnement repose sur l'inspection des métadonnées, la validation des règles de design et la comparaison avec des corpus de référence, permettant ainsi d'éviter les écarts stylistiques et de maintenir une cohérence parfaite.
npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/brandalfGuide la création, la révision et la relecture des actifs de marque Warp ou Oz. À utiliser lors de la conception de pages de lancement, documentation, composants HTML/CSS, maquettes d'interface, prompts, actifs pour réseaux sociaux, copy, présentations ou tout autre livrable de marque qui doit être indubitablement Warp ou Oz.
This repo contains 16 individual skills — each has its own dedicated page.
Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.
Run a model-diverse subagent council to investigate the same problem from multiple perspectives, compare findings, and produce a final recommendation. Use this skill whenever the user asks for a council, second opinions, multiple agents/models to evaluate one question, parallel investigation, red-team/blue-team comparison, or help deciding between competing technical approaches.
Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.
Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.
Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.
Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.
Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.
Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence, and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.
Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.
Walk users through PR review comments, fetching and displaying them first when needed, collect per-comment response decisions, apply requested fixes, and preview GitHub replies and resolutions before posting. Use when responding to PR review comments on the current branch.
Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.
Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.
Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.
Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.
Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.
Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".