by FullAgent
Fulling is an AI-powered Full-stack Engineer Agent. Built with Next.js, Claude, shadcn/ui, and PostgreSQL. Use kubernetes as infra.
# Add to your Claude Code skills
git clone https://github.com/FullAgent/fullingLast scanned: 4/24/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-04-24T06:08:13.014Z",
"semgrepRan": false,
"npmAuditRan": false,
"pipAuditRan": true
}fulling is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by FullAgent. Fulling is an AI-powered Full-stack Engineer Agent. Built with Next.js, Claude, shadcn/ui, and PostgreSQL. Use kubernetes as infra. It has 2,426 GitHub stars.
Yes. fulling passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/FullAgent/fulling" and add it to your Claude Code skills directory (see the Installation section above).
fulling is primarily written in TypeScript. It is open-source under FullAgent on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh fulling against similar tools.
No comments yet. Be the first to share your thoughts!
Fulling is building dedicated AI workspaces: persistent environments that combine skills, files, memory, scripts, and runtime. The current v3 foundation provides the identity and Kubernetes credential boundary required for that product model.
SelfSubjectReviewThe repository intentionally contains no compatibility layer for the previous product model or authentication system.
Read docs/architecture.md for the target Workspace model. The user-level kubeconfig in this foundation is not the final Workspace Runtime ownership model.
Configure the GitHub OAuth callback as:
${BETTER_AUTH_URL}/api/auth/callback/github
corepack pnpm install
cp .env.template .env.local
# Fill in the database, Better Auth, and GitHub values.
corepack pnpm prisma:migrate
corepack pnpm dev
Open http://localhost:3000.
This release uses a new baseline schema. Run it against a new database or an explicitly reset database; it does not migrate v2 data.
corepack pnpm dev # Start the development server
corepack pnpm build # Generate Prisma client and build
corepack pnpm lint # Run ESLint
corepack pnpm test # Run Vitest
corepack pnpm test:e2e # Run Playwright
corepack pnpm prisma:format # Format the Prisma schema
corepack pnpm prisma:validate # Validate the Prisma schema
corepack pnpm prisma:migrate # Deploy the baseline migration
Kubeconfigs are stored as plaintext in PostgreSQL. Database read access grants access to users' Kubernetes credentials. Browser-facing APIs never return saved content, and logs must not contain tokens, keys, certificates, or kubeconfig content.
Validation rejects executable credential plugins, auth-provider plugins, local file credential fields, proxy configuration, non-HTTPS API servers, redirects, and anonymous identities. Authenticated users may still configure an HTTPS API server on any network address. This authenticated outbound-request/SSRF boundary is an explicit deployment decision.
Before replacing a v2 deployment, follow docs/v2-resource-inventory.md. Resetting the Fulling database does not delete Kubernetes resources created by v2.
Use docs/github-oauth-verification.md to verify a real OAuth application before release.