templates

Select and apply project templates for new application scaffolds.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/capaas2/Site-teste --skill templates-capaas2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: templates
Source: https://github.com/capaas2/Site-teste/tree/main/.agent/skills/app-builder/templates
Command: npx skills add https://github.com/capaas2/Site-teste --skill templates-capaas2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you choose and apply the right project scaffold when starting a new application, so you do not have to manually design folder structure, stack choices, and setup conventions from scratch.

Core Features & Use Cases

  • Stack-matched scaffolding: Selects a template based on the app type, such as full-stack web apps, SaaS products, APIs, mobile apps, desktop apps, browser extensions, or CLI tools.
  • Opinionated project structure: Provides clear directory layouts, technology choices, and setup steps for each supported stack.
  • Use Case: A developer wants to start a new SaaS product and needs a Next.js, Prisma, Stripe, and Tailwind-based foundation with the right structure and defaults.

Quick Start

Ask the assistant to create a new project with the appropriate template for your app type, such as a Next.js SaaS app or a FastAPI API.

Frequently Asked Questions about templates

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

FAQPage Schema
How do I scaffold a new SaaS project with Next.js, Prisma, and Stripe without manually setting up the folder structure?

To scaffold a new SaaS project, you select a stack-matched template that provides an opinionated directory layout, predefined technology choices like Next.js and Prisma, and automated setup steps for immediate project initialization.

What is the best way to generate a FastAPI project structure with opinionated conventions for deterministic setup?

Generating a FastAPI project structure involves applying a matching scaffold that enforces opinionated conventions, establishes stack-specific directory layouts, and defines setup steps to ensure deterministic REST API initialization from scratch.

Does this scaffolding tool support setting up full-stack web apps, browser extensions, and CLI tools?

This scaffolding tool supports setting up full-stack web apps, browser extensions, CLI tools, monorepos, mobile apps, desktop apps, and static sites by selecting and applying the correct project template for each specific startup scenario.

Can I use this to establish an app architecture for a monorepo instead of a single-page application?

You can use this to establish an app architecture for a monorepo instead of a single-page application, because it selects the correct project template based on your app type and applies matching opinionated directory structures.

Why should I use an opinionated project template instead of manually configuring my project setup from scratch?

Using an opinionated project template instead of manually configuring project setup saves time by providing clear directory layouts, predefined stack choices, and standardized setup conventions, ensuring deterministic project initialization without manual design.

What are the limitations when applying a matching scaffold to a static site or mobile app?

A limitation when applying a matching scaffold to a static site or mobile app is that the output relies on stack-specific directory structures and opinionated conventions, restricting customization outside the predefined template parameters.