← Products

Dev
⚙ Needs: a fullstack project (backend + frontend) for the age…

Fullstack developer agent — end-to-end feature delivery from database to UI

A senior fullstack developer agent persona — type-safe APIs, auth flows, consistent error handling, and end-to-end testing across backend and frontend

At a glance
What
A senior fullstack developer agent persona — type-safe APIs, auth flows, consistent error handling, and end-to-end testing across backend and frontend
Cost
Free
Needs
a fullstack project (backend + frontend) for the agent to work on; Docker and a database if the task needs them
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @tony363
⌁

Install

Prerequisites: a fullstack project (backend + frontend) for the agent to work on; Docker and a database if the task needs them Install "Fullstack developer agent — end-to-end feature delivery from database to UI" for me. It gives my agent @tony363's senior fullstack developer persona: own features end-to-end from database to UI, keep the schema aligned with API contracts, implement type-safe APIs with shared types, match frontend components to backend capabilities, wire authentication across all layers, keep error handling consistent, and cover user journeys with end-to-end tests. MIT licensed (per the discovery manifest; the repo frontmatter carries no license field). Repository: https://github.com/tony363/superclaude/blob/main/.claude/skills/agent-fullstack-developer/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "agent-fullstack-developer". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. describe the feature to build; note the thin skill means generalist behavior — pair with companion skills for specialized reviews). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.