brandalf

Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups, prompts, social assets, copy, presentations, or any other branded deliverable that should look and sound unmistakably Warp or Oz.

npx skills add https://github.com/warpdotdev/common-skills --skill brandalf

Brandalf

Use this skill as the entrypoint for Warp and Oz branding work.

Source of truth

The canonical brand skill lives at:

https://warp-brand-site.vercel.app/brand/skill

Before creating or revising any Warp- or Oz-branded asset, read that URL and use its contents as the source of truth for:

  • visual style
  • color usage
  • typography
  • voice and tone
  • component rules
  • naming and capitalization
  • implementation guidance

Do not rely on memory when the hosted skill can be fetched.

Workflow

  1. Fetch the hosted brand skill from https://warp-brand-site.vercel.app/brand/skill.
  2. Extract the guidance relevant to the asset being created.
  3. Apply those rules to the requested output.
  4. When presenting the result, briefly note any important brand constraints that materially shaped the output.

Scope

Use Brandalf for assets related to:

  • Warp
  • Oz
  • Warp Drive
  • agentic development / ADE materials that are explicitly branded for Warp or Oz

If the source is unavailable

If the hosted skill cannot be fetched, say that the canonical branding source was unavailable and ask the user whether to proceed with best-effort branding guidance or to retry fetching it.

More skills from warpdotdev

council
warpdotdev
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.
researchcommunicationproject-management
spec-driven-implementation
warpdotdev
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.
developmentdocumentproject-management
review-pr
warpdotdev
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.
code-reviewdevelopment
create-pr
warpdotdev
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.
developmentcode-review
implement-specs
warpdotdev
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.
developmentcode-reviewapi
cross-critique
warpdotdev
Run a second round on a contested question by circulating each subagent's independent proposal to the other authors and asking for structured pros and cons, then synthesize. Use this skill whenever you have multiple independent proposals or opinions on a contested decision — architecture tradeoffs, code review disagreements, design choices, competing root-cause theories — and want sharper analysis than you'd produce by synthesizing alone. Pairs naturally with the council and research skills;...
resolve-merge-conflicts
warpdotdev
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.
developmentcode-review
brandalf
warpdotdev
Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups, prompts, social assets, copy, presentations, or any other branded deliverable that should look and sound unmistakably Warp or Oz.
designcreativemarketing