fullstack-worker

Implements full-stack features spanning Prisma database, Next.js API routes, and React UI.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/fauzanazz/katalis --skill fullstack-worker-fauzanazz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fullstack-worker
Source: https://github.com/fauzanazz/katalis/tree/main/.factory/skills/fullstack-worker
Command: npx skills add https://github.com/fauzanazz/katalis --skill fullstack-worker-fauzanazz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building features that touch the database, API layer, and React UI simultaneously requires coordinating many conventions, tests, translations, and verification steps, which is error-prone when done ad hoc. ## Core Features & Use Cases - Test-Driven Implementation: Writes failing tests first for API routes, React components, and utilities, then implements the minimum code to make them pass. - Full-Stack Coverage: Handles Prisma schema changes, Next.js route handlers with Zod validation, shadcn/ui components with Tailwind, and next-intl translations in English and Indonesian. - Browser Verification: Uses the agent-browser skill to manually verify each user flow in both locales and on mobile viewports before committing. - Use Case: Implement an access-code login feature end to end, including the login page, POST /api/auth/login endpoint, session middleware, tests, translations, and browser-verified flows. ## Quick Start Use the fullstack-worker skill to implement the login feature described in mission.md with tests, translations, and browser verification.

Frequently Asked Questions about fullstack-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a full-stack feature with Next.js and Prisma?▼

Follow a test-driven workflow: write failing tests for API routes and React components first, then implement the minimum code using Prisma for database access, Zod for validation, and shadcn/ui components. Verify with typecheck, lint, and browser testing before committing.

How to test Next.js API route handlers and React components?▼

Write tests covering request validation, response shape, and error cases for API routes, plus rendering, user interaction, and state changes for components. Run the test suite to confirm failures first, then implement until all tests pass.

Does this workflow support multiple languages in Next.js?▼

Yes, it uses next-intl with URL-based locale routing. All user-facing strings must be added to both messages/en.json and messages/id.json, and UI flows are verified in both /en/ and /id/ locales.

When should a feature be returned to the orchestrator instead of implemented?▼

Return when the feature depends on missing database tables or endpoints, preconditions are unmet, a required shadcn/ui component fails to install, tests reveal bugs in prior features, or requirements are ambiguous or contradictory.

What security practices are required when handling user input and uploads?▼

All user input must be sanitized to prevent XSS before storage, and EXIF metadata must be stripped from uploaded images before storage or sending to any AI provider. Secrets must never be included in commits.