eject-sf

Remove SaaS Factory artifacts and scaffolding from a Next.js project.

4|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/JocDLC/saas-factory-v5 --skill eject-sf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eject-sf
Source: https://github.com/JocDLC/saas-factory-v5/tree/main/.claude/skills/eject-sf
Command: npx skills add https://github.com/JocDLC/saas-factory-v5 --skill eject-sf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes SaaS Factory scaffolding and setup from a project, leaving a clean, production-ready app skeleton.

Core Features & Use Cases

  • Safe, guided removal of development artifacts and references to SaaS Factory.
  • Updates to project metadata and READMEs to reflect a vanilla Next.js app.
  • Use Case: A developer wants to distribute or repurpose an app without the factory tooling while preserving core code.

Quick Start

Initiate the eject sequence to remove SaaS Factory artifacts after confirming with the required keyword.

Frequently Asked Questions about eject-sf

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

FAQPage Schema
How do I safely remove SaaS Factory scaffolding from a Next.js project?

Removing SaaS Factory scaffolding requires initiating an eject sequence and confirming the destructive cleanup with a specific keyword. This process deletes factory artifacts while preserving your core Next.js application code.

What happens to my project metadata when ejecting a SaaS Factory template?

Ejecting a SaaS Factory template reverts project metadata to reflect a standard vanilla Next.js app. It also generates a minimal, production-ready base README to replace the original factory documentation.

Can I detach a SaaS Factory template without losing my core application code?

Yes, you can detach the template without losing core code. The guided removal process specifically targets development artifacts and internal references while leaving your essential application files untouched.

When should I perform a destructive cleanup on my Next.js app?

You should perform destructive cleanup when preparing a Next.js app for distribution or handover. This detaches the factory tooling and rebrands the project into a clean, production-ready skeleton.

Do I need to manually update the README after removing SaaS Factory artifacts?

No, you do not need to manually update the README. The eject process automatically generates a minimal, production-ready base README that reflects your cleaned vanilla Next.js project.

What is the best way to rebrand a Next.js app for client handover?

The best way to rebrand a Next.js app for handover is to use a guided eject sequence. This removes factory tooling, reverts metadata, and generates a clean base README for a production-ready skeleton.