{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "kostja94-bricks--build-project-native-footer",
 "repo": "kostja94/bricks",
 "repo_url": "https://github.com/kostja94/bricks",
 "repo_slug": "kostja94-bricks",
 "title": "Build a project-native footer for a SaaS site",
 "page_title": "How to build a project-native footer for a SaaS site with Bricks",
 "summary": "Have an agent build a footer that reuses your primitives and links only to real destinations.",
 "who": "A frontend developer on a bilingual SaaS marketing site who needs a footer that matches the existing routes and design tokens.",
 "problem": "A generated footer often invents routes, imports a second design system, and skips keyboard checks.",
 "outcome": "A footer component built inside the real project, with links to actual product, resource, company, and legal destinations and keyboard access checked on mobile and desktop.",
 "steps": [
  "Install the skill with `npx skills add kostja94/bricks --skill component-builder`.",
  "Tell the agent to read the existing routes, components, design tokens, framework, and responsive conventions before writing code.",
  "Ask the agent to reuse the project's primitives and include only the real product, resource, company, and legal destinations.",
  "Check keyboard access on mobile and desktop inside the actual page, not in an isolated preview."
 ],
 "agent_prompt": "Use the component-builder skill from kostja94/bricks to build the footer for <target project>. Read the existing routes, components, tokens, and framework first, reuse project primitives, and list the file paths you changed. Verify that every footer link points to a real route in the project and that keyboard access works on mobile and desktop.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "Bricks says it does not claim accessibility, performance, or conversion outcomes that were not verified in the target project, so keyboard and link checks are your job.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "javascript",
 "requirements": [
  "A project codebase with routes, components, design tokens, and a frontend framework the agent can read",
  "A coding agent that can run shell commands such as npx in the project",
  "Node.js and npm, needed for npx and for npm test in the Bricks repo"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": true,
 "score": 1.0,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/kostja94-bricks/build-project-native-footer/",
 "md": "https://dedupedai.com/use-cases/kostja94-bricks/build-project-native-footer/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/kostja94-bricks--build-project-native-footer.json",
 "api_version": "v1"
}