agentleFS
Sign inStart free
jshsakurajshsakura/awesome-opencode-skills/skills/fullstack-developer/SKILL.md

fullstack-developer

Skill30 starsChanged 4 months agoMITView on GitHub

Use when one bounded feature or bug spans frontend and backend and a single worker should own the entire path.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use cache-components, frontend-code-review and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mm-mazharSkill

    cache-components

    Expert guidance for Next.js Cache Components and Partial Prerendering (PPR).

    Also in 3 projects that use this

  • chendongqiSkill

    frontend-code-review

    Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.

    Also in 3 projects that use this

  • GoogleSkill

    pr-creator

    Also in 3 projects that use this

  • Hugging FaceSkill

    update-docs

    Update documentation across the repo after API changes. Finds stale references in docs, examples, docstrings, and fixes them.

    Also in 4 projects that use this

  • JetBrainsSkill

    webapp-testing

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    Also in 4 projects that use this

  • VercelSkill

    find-skills

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    ensure request/response semantics match both sides

    line 28
  2. Distinctive:

    ensure UI state handles changed backend behavior safely

    line 29
  3. Distinctive:

    avoid duplicating domain logic across layers

    line 30
  4. Distinctive:

    call out migration impacts if contract shape changes

    line 31
  5. Distinctive:

    verify no unrelated cross-layer churn was introduced

    line 36
  6. Distinctive:

    Do not turn a bounded fullstack task into a broad architecture rewrite unless explicitly requested.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Instructions

Own one complete product path from user action through backend effect and back to UI state.

Working mode:

  1. Trace the end-to-end path and identify boundary contracts.
  2. Implement the smallest coordinated backend + frontend change.
  3. Validate behavior across both layers and the integration seam.

Focus on:

  • UI trigger to backend effect mapping
  • API/event contract alignment
  • shared assumptions across frontend state and backend domain logic
  • error and fallback behavior coherence between layers
  • minimizing surface area while keeping end-to-end correctness

Integration checks:

  • ensure request/response semantics match both sides
  • ensure UI state handles changed backend behavior safely
  • avoid duplicating domain logic across layers
  • call out migration impacts if contract shape changes

Quality checks:

  • validate one full success scenario end-to-end
  • validate one failure scenario end-to-end
  • verify no unrelated cross-layer churn was introduced

Return:

  • full path changed by layer
  • contract and state assumptions involved
  • end-to-end validation performed
  • residual integration risk and follow-up checks

Do not turn a bounded fullstack task into a broad architecture rewrite unless explicitly requested.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free