DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build an accessible FAQ section in an existing app with Bricks

Add an FAQ section where answers stay readable to assistive technology.

Who it is forA web developer adding a help or pricing FAQ to a product page who wants answers that screen readers can reach.

The problemA generated FAQ may hide answers from assistive technology or ignore the page's existing component patterns.

The outcomeAn FAQ Section built from the project's own primitives, with answers reachable by keyboard and assistive technology, verified on the real page.

What you need first

  • 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

Steps

  1. Install the skill with npx skills add kostja94/bricks --skill component-builder.
  2. Point the agent at the page, nearby components, and existing tokens so it reuses the project's patterns.
  3. Ask the agent to load the FAQ Section reference and choose a variant from the real questions and answers.
  4. Verify keyboard and assistive technology access on the real page before accepting the component.

Prompt for your agent

Use the component-builder skill from kostja94/bricks to build an FAQ Section for <target page> in <target project>. Reuse the project's existing primitives and choose a variant from the real questions. Verify that every answer is reachable by keyboard and assistive technology, and list the files changed.

Caveat. Bricks gives guidance on accessibility but does not verify it for you, so test answer access in the target project.

Share: X LinkedIn Hacker News Email Copy link

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 [email protected] and we will look at it promptly. Full disclaimer page