Skip to content
Skills Library
Programming · Building & coding

frontend-application

/frontend-application

Fundamental browser front-end generation in JavaScript. Use for Literate AI workflow tasks that build a page UI. Nested React and WebMCP skills are deltas of this parent.

Repository
literate-ai ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

85/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content20 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Fundamental browser front-end generation in JavaScript. Use for Literate AI workflow tasks that build a page UI. Nested React and WebMCP skills are deltas of this parent.

Original author description

Fundamental browser front-end generation in JavaScript. Use for Literate AI workflow tasks that build a page UI. Nested React and WebMCP skills are deltas of this parent.

How it works

  1. Language and Flavor
  2. Page contract
  3. Modules and npm
  4. Nested realizations
Original SKILL.md headings · 58 lines, 434 words
SKILL.md preview
---
name: "frontend-application"
description: "Fundamental browser front-end generation in JavaScript. Use for Literate AI workflow tasks that build a page UI. Nested React and WebMCP skills are deltas of this parent."
metadata:
  author: "Literate AI maintainers <literate-ai-maintainers@users.noreply.github.com>"
schema: "urn:literate-ai:schema:v1:specification-to-source-skill"
skill_id: "frontend-application"
version: "1.1.0"
title: "Front-end application generation"
stages:
  - "plan"
  - "generate"
dependencies: []
limitations:
  - "Do not generate a front-end under a language Flavor other than JavaScript; a conflicting language Flavor fails closed."
  - "Do not import a generated sibling module through a bare specifier. A bare specifier names an npm package; every generated local module must be imported through an explicit relative path with its file extension."
  - "Do not declare or depend on any npm package unless the package-npm Flavor is selected. Without that Flavor this parent is dependency-free JavaScript; with it, follow javascript-ecosystem lockfile-pinned detect-before-install rules."
  - "Do not treat the portable JSON-in/JSON-out application ABI as the page contract. A browser UI is not a host argv JSON filter."
  - "Do not claim frontend completeness from source inspection, text-presence probes, or a render hash alone; emit browser-observable structure so an authorized verification stage can inspect the rendered page."
trust: "repository-reviewed"
---
# Front-end application generation

Generate a browser-facing front-end in JavaScript. This skill is the reusable UI
parent. Nested React skills add JSX, component structure, and view-state technique.
WebMCP is a nested realization of the MCP parent that also follows this parent: in-page
tools augment the human UI rather than replacing it.

## Language and Flavor

Select this parent only with `lang-javascript`. Selecting it without JavaScript, or
alongside a conflicting language Flavor as the only implementation language, is a
closed failure. React UI structure is an optional `implementation.ui-framework`
Flavor (`ui-react`) constrained to JavaScript; it does not occupy the language axis.
Lockfile-pinned npm is the optional `packaging` Flavor `package-npm`, constrained to
JavaScript and requiring `lang-javascript`.

## Page contract

Keep product behavior in the page: loading and error states stay isolated per panel
so one failed fetch does not blank the rest of the UI. Clean up timers, intervals,
and listeners when the owning view unmounts or the page unloads. Do not invent
interactions the specification did not request.

Render specification-named regions as semantic landmarks with stable accessible names.
Give specified controls durable roles, labels, and state rather than selectors coupled to
generated class names. Loading, empty, unavailable, stale, error, and suppressed states
must remain distinguishable in the rendered document. Preserve unknown numeric values as
unknown; never render `NaN`, `Infinity`, or a fabricated zero.

The page must remain inspectable at desktop and narrow mobile viewports. Contain scrolling
inside regions that are intentionally wide, keep focus visible, and avoid document-level
horizontal overflow unless the specification explicitly requires it. A specified local
interaction must expose its changed state to the accessibility tree and must not perform
an unrelated data fetch.

Browser execution is outside this generation skill's authority. Generate deterministic
fixtures and stable browser-observable seams so the operator-side
`verify-frontend-browser` skill can exercise the built page after host execution is
authorized. Do not embed screenshot baselines, test-only product branches, or acceptance
oracle values in application source.

## Modules and npm

Import every generated sibling through an explicit relative specifier that includes
the file extension (`./App.js`, `./tools.js`). Node and browsers resolve a bare
specifier from `node_modules`. Without `package-npm`, that both fails at runtime for a
dependency-free application and is reported as an undeclared package by dependency
evidence. With `package-npm`, bare specifiers may name lockfile-pinned packages only;
local modules still use relative paths with extensions.

## Nested realizations

- **React dashboard** — delta under this directory: overlaid charts and sortable
  tables over one already-fetched dataset.
- **WebMCP** — delta under `mcp-application/webmcp`: in-page MCP tools. Pin that
  nested skill together with this parent and the MCP parent; do not copy MCP hygiene
  here.
Files in this package (3)
  • SKILL.md 5 KB
  • react-application/SKILL.md 3 KB
  • react-dashboard-application/SKILL.md 4 KB

Versions

The database has no other skills named frontend-application.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version d1c255db1b19 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 85webmcp
    In-page WebMCP tools (JavaScript functions or HTML tools) for front-ends. Use for Literate AI workflow tasks that expose MCP in the browser page. Inherits the MCP parent; not a second protocol.
  • 85react-application
    React JSX component structure, rendering, and local state as a JavaScript UI-framework Flavor. Use for Literate AI workflow tasks when ui-react is selected. Delta of the front-end parent.
  • 100add-webmcp
    Analyze an existing web application, identify safe user-visible capabilities across routes, forms, server actions, handlers, and schemas, then implement first-party WebMCP tools and validate discovery and invocation with Stagehand. Use when the user asks to make a codebase…
  • 90webmcp-site-tools
    Design, implement, audit, and test WebMCP Site tools exposed by an existing web application through document.modelContext.registerTool. Use when an app should offer agent-facing actions in the live signed-in page or when Agent Graph needs a semantic browser verification lane. Do…
  • 90implement
    Add WebMCP tools to a website codebase so browser agents can act through the site's own logic instead of scraping the page. Use when asked to make a site agent-ready or WebMCP-ready, add WebMCP or document.modelContext tools, or implement site tools with @nekuda/webmcp-sdk.
  • 100webmcp-gen
    Create, compile, and validate site-specific WebMCP init scripts from a target URL and desired tool capability. Use when the user wants to author WebMCP tools for a website, produce a webmcp.init.js artifact, or test WebMCP registration and invocation through Stagehand.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.