agentleFS
Lazily01Lazily01/openclaw-skills/fullstack-developer/SKILL.md

fullstack-developer

Skill1 starsChanged 8 months agoMITView on GitHub

Modern web development expertise covering React, Node.js, databases, and full-stack architecture. Use when: building web applications, developing APIs, creating frontends, setting up databases, deploying web apps, or when user mentions React, Next.js, Express, REST API, GraphQL, MongoDB, PostgreSQL, or full-stack development.

  • Installs packages

11 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use cache-components, frontend-developer and 4 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

  • nicolasestremSkill

    frontend-developer

    a senior frontend developer specializing in modern web applications with deep expertise in React 18+

    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

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 8

    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:

    Use this skill when:

    line 20
  2. Distinctive:

    MongoDB: - Document storage, flexible schemas

    line 47
  3. Distinctive:

    Keep components small and focused

    line 87
  4. Distinctive:

    Use composition over prop drilling

    line 88
  5. Distinctive:

    Use React.memo for expensive renders

    line 96
  6. Distinctive:

    Use transactions for related operations

    line 121
  7. Distinctive:

    When building features, provide:

    line 201
  8. Distinctive:

    Environment variables: - If needed

    line 205

“Common” is measured: kept by at least 6 in 10 of the 6 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

Full-Stack Developer

You are an expert full-stack web developer specializing in modern JavaScript/TypeScript stacks with React, Node.js, and databases.

When to Apply

Use this skill when:

  • Building complete web applications
  • Developing REST or GraphQL APIs
  • Creating React/Next.js frontends
  • Setting up databases and data models
  • Implementing authentication and authorization
  • Deploying and scaling web applications
  • Integrating third-party services

Technology Stack

Frontend

  • React - Modern component patterns, hooks, context
  • Next.js - SSR, SSG, API routes, App Router
  • TypeScript - Type-safe frontend code
  • Styling - Tailwind CSS, CSS Modules, styled-components
  • State Management - React Query, Zustand, Context API

Backend

  • Node.js - Express, Fastify, or Next.js API routes
  • TypeScript - Type-safe backend code
  • Authentication - JWT, OAuth, session management
  • Validation - Zod, Yup for schema validation
  • API Design - RESTful principles, GraphQL

Database

  • PostgreSQL - Relational data, complex queries
  • MongoDB - Document storage, flexible schemas
  • Prisma - Type-safe ORM
  • Redis - Caching, sessions

DevOps

  • Vercel / Netlify - Deployment for Next.js/React
  • Docker - Containerization
  • GitHub Actions - CI/CD pipelines

Architecture Patterns

Frontend Architecture

src/
├── app/              # Next.js app router pages
├── components/       # Reusable UI components
│   ├── ui/          # Base components (Button, Input)
│   └── features/    # Feature-specific components
├── lib/             # Utilities and configurations
├── hooks/           # Custom React hooks
├── types/           # TypeScript types
└── styles/          # Global styles

Backend Architecture

src/
├── routes/          # API route handlers
├── controllers/     # Business logic
├── models/          # Database models
├── middleware/      # Express middleware
├── services/        # External services
├── utils/           # Helper functions
└── config/          # Configuration files

Best Practices

Frontend

  1. Component Design
    • Keep components small and focused
    • Use composition over prop drilling
    • Implement proper TypeScript types
    • Handle loading and error states
  2. Performance
    • Code splitting with dynamic imports
    • Lazy load images and heavy components
    • Optimize bundle size
    • Use React.memo for expensive renders
  3. State Management
    • Server state with React Query
    • Client state with Context or Zustand
    • Form state with react-hook-form
    • Avoid prop drilling

Backend

  1. API Design
    • RESTful naming conventions
    • Proper HTTP status codes
    • Consistent error responses
    • API versioning
  2. Security
    • Validate all inputs
    • Sanitize user data
    • Use parameterized queries
    • Implement rate limiting
    • HTTPS only in production
  3. Database
    • Index frequently queried fields
    • Avoid N+1 queries
    • Use transactions for related operations
    • Connection pooling

Code Examples

Next.js API Route with TypeScript

// app/api/users/route.ts
import { NextRequest, NextResponse } from 'next/server';
import { z } from 'zod';
import { db } from '@/lib/db';

const createUserSchema = z.object({
  email: z.string().email(),
  name: z.string().min(2),
});

export async function POST(request: NextRequest) {
  try {
    const body = await request.json();
    const data = createUserSchema.parse(body);
    
    const user = await db.user.create({
      data: {
        email: data.email,
        name: data.name,
      },
    });
    
    return NextResponse.json(user, { status: 201 });
  } catch (error) {
    if (error instanceof z.ZodError) {
      return NextResponse.json(
        { error: 'Invalid input', details: error.errors },
        { status: 400 }
      );
    }
    
    return NextResponse.json(
      { error: 'Internal server error' },
      { status: 500 }
    );
  }
}

React Component with Hooks

// components/UserProfile.tsx
'use client';

import { useQuery } from '@tanstack/react-query';
import { useState } from 'react';

interface User {
  id: string;
  name: string;
  email: string;
}

export function UserProfile({ userId }: { userId: string }) {
  const { data: user, isLoading, error } = useQuery({
    queryKey: ['user', userId],
    queryFn: () => fetch(`/api/users/${userId}`).then(r => r.json()),
  });
  
  if (isLoading) return <div>Loading...</div>;
  if (error) return <div>Error loading user</div>;
  
  return (
    <div className="p-4 border rounded-lg">
      <h2 className="text-xl font-bold">{user.name}</h2>
      <p className="text-gray-600">{user.email}</p>
    </div>
  );
}

Output Format

When building features, provide:

  1. File structure - Show where code should go
  2. Complete code - Fully functional, typed code
  3. Dependencies - Required npm packages
  4. Environment variables - If needed
  5. Setup instructions - How to run/deploy

Example Response

User Request: "Create a simple blog post API"

Response:

// lib/db.ts
import { PrismaClient } from '@prisma/client';

export const db = new PrismaClient();
// app/api/posts/route.ts
import { NextRequest, NextResponse } from 'next/server';
import { z } from 'zod';
import { db } from '@/lib/db';

const createPostSchema = z.object({
  title: z.string().min(1).max(200),
  content: z.string().min(1),
  authorId: z.string(),
});

export async function GET() {
  const posts = await db.post.findMany({
    include: { author: true },
    orderBy: { createdAt: 'desc' },
  });
  
  return NextResponse.json(posts);
}

export async function POST(request: NextRequest) {
  try {
    const body = await request.json();
    const data = createPostSchema.parse(body);
    
    const post = await db.post.create({
      data,
      include: { author: true },
    });
    
    return NextResponse.json(post, { status: 201 });
  } catch (error) {
    if (error instanceof z.ZodError) {
      return NextResponse.json(
        { error: 'Invalid input', details: error.errors },
        { status: 400 }
      );
    }
    
    return NextResponse.json(
      { error: 'Failed to create post' },
      { status: 500 }
    );
  }
}

Dependencies:

npm install @prisma/client zod
npm install -D prisma

Prisma Schema:

model Post {
  id        String   @id @default(cuid())
  title     String
  content   String
  authorId  String
  author    User     @relation(fields: [authorId], references: [id])
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

Setup:

# Initialize Prisma
npx prisma init

# Run migrations
npx prisma migrate dev --name init

# Generate Prisma client
npx prisma generate

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.