Chromestatus Frontend
Developmentchromestatus-frontendChromestatus Frontend is an Agent Skill for development published in the GoogleChrome/chromium-dashboard repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Guidance for working on the Lit-based frontend, Shoelace widgets, and client-side routing in chromium-dashboard.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/GoogleChrome/chromium-dashboard/blob/HEAD/.agents/skills/chromestatus-frontend/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/chromestatus-frontend, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Frontend Development Skill
This skill provides context and guidelines for developing the frontend of the chromium-dashboard project.
Core Technologies
- Lit: The primary library for building web components.
- Shoelace: A collection of high-quality UI widgets used throughout the application.
- page.js: A micro client-side router for SPA navigation.
- Rollup: Used for bundling and code-splitting JavaScript.
Key Directories
client-src/elements/: Contains Lit web components.client-src/js-src/: General JavaScript source files, includingcs-client.js.client-src/css/: CSS files and Lit style modules.static/dist/: Output directory for bundled assets.templates/: Jinja2 templates for the initial page load skeleton.
Guidelines
- Component Development: Create new components in
client-src/elements/. Follow the naming conventionchromedash-*.js. - Icons: Prefer Material Icons. If using Bootstrap icons via Shoelace, ensure they are copied to
static/shoelace/assets/icons. - API Interaction: Use the client wrapper in
cs-client.jsor the OpenAPI context consumer for making server requests. - Styling: Use Lit's
csstagged templates for component styles. Leverage variables from the design system where possible. - Legacy Code: Do not add new code or components to the legacy
pages/directory on the backend, even if it contains old templates. All newer frontend logic should reside inclient-src/.
Common Tasks
- Adding a New Page: Register the route in
chromedash-app.js(withinsetUpRoutes) and create the corresponding Lit component. - Building assets: Use
make watchduring development for live-reloading ormake buildfor a final build.