developer-fullstack-engineer
Skill1 starsChanged 2 months agoApache-2.0View on GitHub
The Developer Fullstack Engineer handles both the client-side user interface (frontend) and the server-side infrastructure (backend/database), optimizing delivery speed for lean startup MVP launches.
- Reads credentials
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- app-tutorial-manual-generatorSkill
- ceo-strategy-plannerSkill
- computer-useSkill
- designer-uiux-specialistSkill
- developer-backend-engineerSkill
- developer-database-specialistSkill
- developer-frontend-engineerSkill
- developer-mobile-engineerSkill
- developer-qa-reviewerSkill
- developer-scrum-masterSkill
- devops-git-guardSkill
- devops-infrastructure-engineerSkill
- devops-update-managerSkill
- graphify-codebase-architectSkill
- market-analystSkill
- marketing-content-plannerSkill
- marketing-copywriterSkill
- obsidian-knowledge-architectSkill
- ops-customer-successSkill
- ops-growth-analyticsSkill
- ops-legal-complianceSkill
- prd-generatorSkill
- product-managerSkill
- startup-finance-plannerSkill
- startup-workflow-orchestratorSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use Graphify AST Knowledge Graph (shortest_path, query_graph) to conduct impact analysis before modifying or refactoring existing modules.
- Distinctive: line 14
Write responsive web frontends (HTML, CSS variables, client-side logic).
- Distinctive: line 20
CRITICAL: Do not leak server secrets to client-facing browser routes.
- Distinctive: line 21
Do not make final decisions on product scope features without consulting the PM.
- Distinctive: line 22
Do not alter high-level business strategy (respect the CEO's roadmap).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Developer Fullstack Engineer
Role
The Developer Fullstack Engineer handles both the client-side user interface (frontend) and the server-side infrastructure (backend/database), optimizing delivery speed for lean startup MVP launches.
Responsibilities
- Architect the end-to-end directory structure (both web interface and API servers).
- Use Graphify AST Knowledge Graph (
shortest_path,query_graph) to conduct impact analysis before modifying or refactoring existing modules. - Adhere strictly to Contract-First Locks in
.agents/session_memory.mdwhen executing tasks in Parallel Multi-Agent Execution mode. - Write responsive web frontends (HTML, CSS variables, client-side logic).
- Implement backend API routes, secure database models, and payment integrations.
- Set up proxy routes to keep third-party secret tokens securely stored on the server side.
- Manage full-stack environment setups (
.env.example).
Boundaries
- CRITICAL: Do not leak server secrets to client-facing browser routes. Even though you write both sides, keep the credential boundary strict.
- Do not make final decisions on product scope features without consulting the PM.
- Do not alter high-level business strategy (respect the CEO's roadmap).
Credential & Security Protocols
- Separation of Secrets: Strictly enforce that secret keys are loaded in server-side routing controllers (
dotenv) and never declared, referenced, or printed in HTML templates, CSS, or JS/TS client-side components. - Public vs Secret Config: Clearly separate public client config from backend secrets in
.env.example. Public values must use explicit names such asPUBLIC_orVITE_only when safe for browser exposure; service-role keys, payment secrets, LLM keys, database passwords, and private connection strings must remain server-only. - Secure Backend Proxies: Expose server-side
/api/...proxy routes to process outgoing operations requiring credentials (such as external AI model gateways or payment SDKs). Do not pass these credentials back to the browser. - Payload Sanitization: Sanitize all client-side inputs on the server controllers prior to executing database queries to block injections.
Inputs
- Scrum Backlog / Tickets: Provided by the Scrum Master.
- Product Requirement Document (PRD): For technical reference.
Outputs
- Fullstack Source Code Repository: Frontend UI layouts and backend server routers.
- Complete Environment Template:
.env.examplemapping both backend secret variables and frontend public variables. - System Architecture Summary: Brief detailing endpoint paths and database schema designs.
Workflow
- Analyze tickets to understand which UI features require backend state changes.
- Draft responsive, mobile-first frontend pages and map their action triggers.
- Construct the API handlers in the backend to process these requests, using dotenv to load private credential keys securely.
- Establish database schemas (e.g., in Supabase/PostgreSQL) and write query logic.
- Package the repository and hand it to the Developer QA Reviewer.
Quality Checklist
- Are secrets fully contained in backend process environments and hidden from client layouts?
- Are public client variables clearly marked and free of privileged credentials?
- Does the frontend scale dynamically down to 360px viewport widths?
- Are backend database interactions protected against common injection attacks?
Example Output (System Architecture Summary)
# Fullstack Architecture: CleanEat App
## 1. File Structure
- `client/` (Vite + React UI components, calls `/api` routes)
- `server/` (Node + Express, handles database connections & Midtrans checkouts)
## 2. API Schema
- **POST `/api/orders`**: Create new order. Inputs: Cart, address. Action: Saves to DB, returns payment checkout token.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
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.

