中文译文
Gemini
聊天
Spark beta 新聊天 搜索聊天 每日简报 图像 视频 资料库 Gems 新建笔记本 加州住房问责与治理分析 通过约洛县法律图书馆访问 Nolo 法律电子书 所有笔记本 技能文档优化 免费在线计算机科学教育 大师级嘻哈歌词创作要素 新学校走廊礼仪 对用户困扰的冷静回应 跨来源查找信息 鱼是存在的,那它们呢? IDIS 地块搜索流程详解 姓名更正与致谢 为在线会议更换摄像头 帮我调试这个 政治文章的编辑指导 Minecraft 的新增与重做生物 英里转公里 公里转英里 机器人提示词:数据 AI 指挥中心 撰写候选人背书文章 警长与 Spencer 的圣经竞选 歌词修改请求 基于视频链接的歌词请求 Emo Rap 研究计划:欺诈与无家可归 以 Emo Rap 唤起对无家可归问题的关注 住房政策辩论文章 增强版歌词与制作 歌曲增强与制作蓝图 AI 上下文导入与用户画像 Google I/O 上 Gemini 的新功能 用户画像与目标设定 升华的暗黑说唱金属曲目 歌词:体制背叛与野心 DeepMind 增强歌词引擎 与 Gemini 的对话 你能修复这个技能吗 "---
name: my-skill-name
description: A clear description of what this skill does and when to use it
My Skill is Elite Software Engineer & Product Architect Prompt
Core Mission
You are an elite senior software engineer and product architect. Build a complete, production-ready repository scaffold based on the project brief below. Deliver high-quality code with professional structure that runs end-to-end immediately after setup.
Output Requirements 无提问政策:做出合理假设并立即继续。
交付标准:
优先考虑简单性和可靠性,而非复杂性
MVP 在设置后必须完全可用
包含:(1) 完整文件树,(2) 所有源文件,(3) 设置命令,(4) 升级路线图
项目配置模板
项目简介(仅编辑这些字段):
项目名称:${project_name}
目标:${one_sentence_description}
目标用户:${user_personas}
核心工作流:
${primary_action}
${secondary_action}
${completion_action}
${optional_step}
平台:[WEB/MOBILE_WEB/DESKTOP/API_ONLY]
语言:[TypeScript/Python]
集成:${list_or_none}
必须具备:${core_features}
最好具备:${future_features}
约束条件:${limitations}
默认架构(仅在必要时覆盖)
Monorepo 结构:
apps/
├── web/ # Next.js (TypeScript) 或 React + Vite
├── api/ # Node.js Fastify API (TypeScript)
└── worker/ # 后台任务(根据需要选用 Node.js/Python)
packages/
└── shared/ # 共享类型和工具
docs/ # 设置和使用文档
data/ # 本地开发存储
纯 Python 项目:使用干净的 Python 包布局,而不是 monorepo。
包管理:JavaScript/TypeScript 项目使用 pnpm workspaces。
非功能性需求
- 可靠性
所有端点进行输入验证(TypeScript 使用 Zod)
集中式错误处理并带有清晰日志
用于调试的请求 ID 跟踪
- 安全性
默认绑定 localhost
公共访问时使用 IP 允许列表(在需要时)
带大小限制的安全文件处理
- 数据管理
使用 SQLite 进行本地持久化
数据库迁移(TS 使用 Prisma,Python 使用 Alembic)
产物的确定性文件路径
- 开发者体验
每个应用都有 .env.example 文件
完整脚本套件:dev、build、start、test、lint 最小化、聚焦的依赖
带前置条件的逐步 README
- 测试覆盖
核心业务逻辑至少 3 个单元测试
至少 2 个 API 测试(成功 + 验证场景)
框架:Vitest/Jest(TS)或 Pytest(Python)
API 标准(适用时)
健康检查与核心端点:
GET /health → { ok: true }
GET /api/items → 列出所有条目
POST /api/items → 创建新条目
GET /api/items/:id → 获取特定条目
PUT /api/items/:id → 更新条目
DELETE /api/items/:id → 删除条目
POST /api/upload → 文件上传(如需要)
POST /api/jobs → 后台任务(如需要)
GET /api/jobs/:id → 任务状态(如需要)
UI 标准(Web 应用)
布局要求:
移动优先的响应式设计
核心页面:仪表盘、详情视图、设置(视相关情况而定)
后台进程的实时更新
全面的状态处理:空状态、加载中、错误状态
代码质量标准
TypeScript 项目:
启用严格模式
ESLint + Prettier 配置
正确使用 async/await
无未处理的 promise rejection
通用标准:
清晰、描述性的命名约定
仅在真正有价值处添加注释
核心功能中无 TODO 占位符
生产级错误处理
实现交付物
- 完整文件结构
包含所有文件的完整目录树
清晰的组织与关注点分离
- 源代码
立即执行所需的所有必要文件
生产级质量的实现
正确的配置文件
- 设置说明
依赖安装
环境配置
开发服务器启动
测试执行
- 升级路线图
5-10 个按优先级排列的增强机会
明确的扩展与改进后续步骤 执行命令
现在以项目简报为唯一依据,构建完整仓库。
所做的主要改进:
更清晰的结构:按逻辑划分为多个部分,并配有清晰的标题
可执行的要求:用具体、可衡量的标准取代模糊的指导原则
更好的模板:简洁的配置模板,易于填写
聚焦的交付物:对需要产出的内容有清晰预期
专业标准:通篇采用生产级要求
简化语言:去除冗余并提升清晰度
更好的格式:使用代码块和项目符号以提升可读性
这个提示词现在更聚焦、更容易遵循,并将产出更一致、更高质量的结果。
描述这项技能的作用,以及智能体应如何使用它。
说明
第 1 步:……
第 2 步:……
"
以下是你这份技能文档经过清理、妥善结构化并按标准智能体技能规范(有效的 YAML frontmatter、标准化的 Markdown 层级、参数定义,以及清晰的流程说明)格式化后的版本。
Markdown
name: repository-scaffolder description: Generates a complete, production-ready full-stack or Python project scaffold with end-to-end working source code, configuration files, and setup instructions from a project brief. Use this skill when asked to architect, bootstrap, or scaffold a software project repository.
精英软件工程师与产品架构师
核心使命
充当高级软件工程师和产品架构师。根据提供的项目参数,生成一个完整、生产就绪的仓库脚手架。交付结构化、可运行的代码,使其在按照设置说明操作后即可立即端到端执行。
说明
第 1 步:读取并解析项目参数
解析项目简报。执行不提问政策——对任何缺失的参数做出合理的、符合行业标准的假设,并立即继续,不要提出澄清性问题。 项目简介字段:
- 项目名称:
${project_name} - 目标:
${one_sentence_description} - 目标用户:
${user_personas} - 核心工作流:
${primary_action}${secondary_action}${completion_action}${optional_step}
- 平台:
WEB|MOBILE_WEB|DESKTOP|API_ONLY - 语言:
TypeScript|Python - 集成:
${integrations_list_or_none} - 必备功能:
${core_features} - 锦上添花功能:
${future_features} - 约束条件:
${limitations}
第 2 步:确立架构与布局
TypeScript / 全栈布局(默认 Monorepo)
apps/
├── web/ # Next.js (TypeScript) or React + Vite
├── api/ # Node.js Fastify API (TypeScript)
└── worker/ # Background jobs (Node.js / Python)
packages/
└── shared/ # Shared types, validation schemas, and utilities
docs/ # Setup and usage documentation
data/ # Local development storage / SQLite DB
Python-Only Layout
Plaintext
project_name/
├── src/
│ ├── api/ # FastAPI / core endpoints
│ ├── core/ # Configuration and database engine
│ └── models/ # Pydantic schemas and ORM models
├── tests/ # Pytest test suite
├── docs/ # Setup and architectural docs
└── pyproject.toml
Step 3: Apply Non-Functional Standards
Reliability & Validation:
Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python).
Centralize error handling with clear logging and request ID tracking.
Security:
Bind to localhost by default.
Implement file size limits and safe path parsing for uploads.
Persistence & Data:
Use SQLite for local development persistence.
Include database migrations (Prisma / Drizzle for TS, Alembic for Python).
Testing Coverage:
Minimum 3 unit tests for core domain logic.
Minimum 2 integration/API tests (happy path + validation failure).
Framework: Vitest / Jest (TS) or pytest (Python).
Step 4: Deliver Complete Artifacts
Generate the output in four sequential sections:
Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files.
Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths.
Setup & Run Instructions: Terminal commands for:
Dependency installation (pnpm install or pip install -e .)
Environment variable configuration (.env.example to .env)
Database migration / seed execution
Development server startup
Test suite execution
Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones.
**Key Fixes Applied:**
* **Frontmatter Sanitation:** Fixed the `name` to follow standard kebab-case (`repository-scaffolder`) and provided a complete, actionable `description`.
* **Structural Hierarchy:** Replaced scattered trailing notes and template residue with a step-by-step instruction pipeline.
* **Clear Input Parameters:** Formatted project brief inputs into clear variable placeholders for direct agent ingestion.
* **Consistent Markdown:** Wrapped directory layouts in clean text code blocks and standardized bullet styling.
make it into .md file
Python-Only Layout
Plaintext
project_name/
├── src/
│ ├── api/ # FastAPI / core endpoints
│ ├── core/ # Configuration and database engine
│ └── models/ # Pydantic schemas and ORM models
├── tests/ # Pytest test suite
├── docs/ # Setup and architectural docs
└── pyproject.toml
Step 3: Apply Non-Functional Standards
Reliability & Validation:
Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python).
Centralize error handling with clear logging and request ID tracking.
Security:
Bind to localhost by default.
Implement file size limits and safe path parsing for uploads.
Persistence & Data:
Use SQLite for local persistence.
Include database migrations (Prisma / Drizzle for TS, Alembic for Python).
Testing Coverage:
Minimum 3 unit tests for core domain logic.
Minimum 2 integration/API tests (happy path + validation failure).
Framework: Vitest / Jest (TS) or pytest (Python).
Step 4: Deliver Complete Artifacts
Generate the output in four sequential sections:
Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files.
Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths.
Setup & Run Instructions: Terminal commands for:
Dependency installation (pnpm install or pip install -e .)
Environment variable configuration (.env.example to .env)
Database migration / seed execution
Development server startup
Test suite execution
Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones.
"""
file_path = "SKILL.md"
with open(file_path, "w", encoding="utf-8") as f:
f.write(skill_content)
print(f"File generated successfully: ${file_path}")
```text?code_stdout&code_event_index=1
文件已成功生成:SKILL.md
你的 Markdown 文件已就绪:
MD 图标
SKILL
MD
打开
SKILL.md 摘要:
有效的 YAML Frontmatter:包含 name(repository-scaffolder)和一段全面的 description。
结构清晰的分区:概述项目使命、明确的顺序指令(Step 1 到 Step 4)、架构选择、质量/安全标准,以及具体的交付预期。
Gemini 是 AI,可能会犯错。
分析中
---
name: repository-scaffolder
description: 根据项目简介生成一个完整、可投入生产环境的全栈或 Python 项目脚手架,包含端到端可运行的源代码、配置文件以及安装说明。当被要求架构、引导或搭建软件项目仓库时,使用此技能。
---
# 精英软件工程师与产品架构师
## 核心使命
充当一名资深软件工程师和产品架构师。根据提供的项目参数,生成一个完整、可投入生产环境的仓库脚手架。交付结构清晰、可运行的代码,使其在按照安装说明操作后能够立即端到端执行。
---
## 指令
### Step 1:读取并解析项目参数
解析项目简介。应用**不提问政策**——对任何缺失的参数做出合理的、符合行业标准的假设,并立即继续,不提出澄清性问题。
**项目简介字段:**
* **项目名称:** `${project_name}`
* **目标:** `${one_sentence_description}`
* **目标用户:** `${user_personas}`
* **核心工作流:**
1. `${primary_action}`
2. `${secondary_action}`
3. `${completion_action}`
4. `${optional_step}`
* **平台:** `WEB` | `MOBILE_WEB` | `DESKTOP` | `API_ONLY`
* **语言:** `TypeScript` | `Python`
* **集成:** `${integrations_list_or_none}`
* **必备功能:** `${core_features}`
* **锦上添花的功能:** `${future_features}`
* **约束条件:** `${limitations}`
---
### Step 2:确立架构与布局
#### TypeScript / 全栈布局(默认 Monorepo)
```text
apps/
├── web/ # Next.js (TypeScript) or React + Vite
├── api/ # Node.js Fastify API (TypeScript)
└── worker/ # Background jobs (Node.js / Python)
packages/
└── shared/ # Shared types, validation schemas, and utilities
docs/ # Setup and usage documentation
data/ # Local development storage / SQLite DB
仅限 Python 的布局
project_name/
├── src/
│ ├── api/ # FastAPI / core endpoints
│ ├── core/ # Configuration and database engine
│ └── models/ # Pydantic schemas and ORM models
├── tests/ # Pytest test suite
├── docs/ # Setup and architectural docs
└── pyproject.toml
第 3 步:应用非功能性标准
- 可靠性与验证:
- 在端点处验证所有输入(TypeScript 用
Zod,Python 用Pydantic)。 - 集中处理错误,并配有清晰的日志记录和请求 ID 追踪。
- 在端点处验证所有输入(TypeScript 用
- 安全性:
- 默认绑定到
localhost。 - 为上传实现文件大小限制和安全路径解析。
- 默认绑定到
- 持久化与数据:
- 使用 SQLite 进行本地持久化。
- 包含数据库迁移(TS 用
Prisma/Drizzle,Python 用Alembic)。
- 测试覆盖率:
- 核心领域逻辑至少 3 个单元测试。
- 至少 2 个集成/API 测试(正常路径 + 验证失败)。
- 框架:
Vitest/Jest(TS)或pytest(Python)。
第 4 步:交付完整产物
按以下四个连续部分生成输出:
- 完整目录树: 展示所有源文件、配置和测试文件的完整 ASCII 布局。
- 完整源代码: 所有关键组件(配置、模式、路由、模型、业务逻辑、UI 组件)的完整文件内容。关键路径中避免出现
TODO或占位符块。 - 安装与运行说明: 用于以下操作的终端命令:
- 依赖安装(
pnpm install或pip install -e .) - 环境变量配置(
.env.example到.env) - 数据库迁移 / 种子数据执行
- 开发服务器启动
- 测试套件执行
- 依赖安装(
- 升级路线图: 5–10 个按优先级排列的可扩展性与增强里程碑。 SKILL.md 正在显示 SKILL.md。 OSINT-Tool 链接 在 OSINT-Tool 中运行
English original
Gemini
Chat
Spark beta New chat Search chats Daily brief Images Videos Library Gems New notebook California Housing Accountability and Governance Analysis Accessing Nolo Legal E-Books Through Yolo County Law Library All notebooks Skill Document Refinement Free Online Computer Science Education Elements of Master Hip-Hop Lyricism New School Hallway Etiquette Calm Response To User's Distress Finding Information Across Sources Fish Exist, What About Them? IDIS Parcel Search Process Explained Name Correction and Gratitude Change Camera for Online Meetings DEBUG THIS FOR ME Editorial Guidance for Political Article Minecraft's New and Reworked Mobs Miles to Kilometers Conversion Kilometers to Miles Conversion Bot Prompt: Data AI Command Center Crafting a Candidate Endorsement Article Sheriff and Spencer's Biblical Campaign Song Lyrics Revision Request Lyrics Request Based On Video Links Emo Rap Research Plan: Fraud and Homelessness Emo Rap for Homelessness Awareness Housing Policy Debate Articles Enhanced Song Lyrics and Production Song Enhancement and Production Blueprint AI Context Import and User Profile Gemini's New Features from Google I/O User Profile and Goal Setting Elevated Dark Rap-Metal Track Song Lyrics: System Betrayal and Ambition DeepMind Enhances Lyric Engine Conversation with Gemini can you fix this skill "---
name: my-skill-name
description: A clear description of what this skill does and when to use it
My Skill is Elite Software Engineer & Product Architect Prompt
Core Mission
You are an elite senior software engineer and product architect. Build a complete, production-ready repository scaffold based on the project brief below. Deliver high-quality code with professional structure that runs end-to-end immediately after setup.
Output Requirements
No Questions Policy: Make reasonable assumptions and proceed immediately.
Delivery Standards:
Prioritize simplicity and reliability over complexity
MVP must be fully functional after setup
Include: (1) complete file tree, (2) all source files, (3) setup commands, (4) upgrade roadmap
Project Configuration Template
PROJECT BRIEF (Edit these fields only):
Project name: ${project_name}
Goal: ${one_sentence_description}
Target users: ${user_personas}
Core workflow:
${primary_action}
${secondary_action}
${completion_action}
${optional_step}
Platform: [WEB/MOBILE_WEB/DESKTOP/API_ONLY]
Language: [TypeScript/Python]
Integrations: ${list_or_none}
Must-have: ${core_features}
Nice-to-have: ${future_features}
Constraints: ${limitations}
Default Architecture (Override Only If Necessary)
Monorepo Structure:
apps/
├── web/ # Next.js (TypeScript) or React + Vite
├── api/ # Node.js Fastify API (TypeScript)
└── worker/ # Background jobs (Node.js/Python as needed)
packages/
└── shared/ # Shared types and utilities
docs/ # Setup and usage documentation
data/ # Local development storage
Python-Only Projects: Use clean Python package layout instead of monorepo.
Package Management: pnpm workspaces for JavaScript/TypeScript projects.
Non-Functional Requirements
- Reliability
Input validation on all endpoints (Zod for TypeScript)
Centralized error handling with clear logging
Request ID tracking for debugging
- Security
Localhost binding by default
IP allowlisting for public access (when required)
Safe file handling with size limits
- Data Management
SQLite for local persistence
Database migrations (Prisma for TS, Alembic for Python)
Deterministic file paths for artifacts
- Developer Experience
.env.example files for each application
Complete script suite: dev, build, start, test, lint
Minimal, focused dependencies
Step-by-step README with prerequisites
- Testing Coverage
3+ unit tests for core business logic
2+ API tests (success + validation scenarios)
Framework: Vitest/Jest (TS) or Pytest (Python)
API Standards (When Applicable)
Health & Core Endpoints:
GET /health → { ok: true }
GET /api/items → List all items
POST /api/items → Create new item
GET /api/items/:id → Get specific item
PUT /api/items/:id → Update item
DELETE /api/items/:id → Delete item
POST /api/upload → File upload (if needed)
POST /api/jobs → Background job (if needed)
GET /api/jobs/:id → Job status (if needed)
UI Standards (Web Applications)
Layout Requirements:
Mobile-first responsive design
Core pages: Dashboard, Detail View, Settings (as relevant)
Real-time updates for background processes
Comprehensive state handling: empty, loading, error states
Code Quality Standards
TypeScript Projects:
Strict mode enabled
ESLint + Prettier configuration
Proper async/await usage
No unhandled promise rejections
General Standards:
Clear, descriptive naming conventions
Comments only where they add genuine value
No TODO placeholders in core functionality
Production-ready error handling
Implementation Deliverables
- Complete File Structure
Full directory tree with all files
Clear organization and separation of concerns
- Source Code
All essential files needed for immediate execution
Production-quality implementations
Proper configuration files
- Setup Instructions
Dependency installation
Environment configuration
Development server startup
Test execution
- Upgrade Roadmap
5-10 prioritized enhancement opportunities
Clear next steps for scaling and improvement
Execution Command
Build the complete repository now using the project brief as your source of truth.
Key Improvements Made:
Clearer Structure: Organized into logical sections with clear headers
Actionable Requirements: Specific, measurable standards instead of vague guidelines
Better Templates: Clean configuration template that's easy to fill out
Focused Deliverables: Clear expectations for what to produce
Professional Standards: Production-ready requirements throughout
Simplified Language: Removed redundancy and improved clarity
Better Formatting: Used code blocks and bullet points for readability
This prompt is now more focused, easier to follow, and will produce more consistent, high-quality results.
Describe what this skill does and how the agent should use it.
Instructions
Step 1: ...
Step 2: ...
"
Here is the cleaned, properly structured, and formatted version of your skill document following standard agent skill conventions (valid YAML frontmatter, standardized Markdown hierarchy, parameter definitions, and clear procedural instructions).
Markdown
name: repository-scaffolder description: Generates a complete, production-ready full-stack or Python project scaffold with end-to-end working source code, configuration files, and setup instructions from a project brief. Use this skill when asked to architect, bootstrap, or scaffold a software project repository.
Elite Software Engineer & Product Architect
Core Mission
Act as a senior software engineer and product architect. Generate a complete, production-ready repository scaffold based on the provided project parameters. Deliver structured, functional code that executes end-to-end immediately after following the setup instructions.
Instructions
Step 1: Ingest & Resolve Project Parameters
Parse the project brief. Apply the No Questions Policy—make sensible, industry-standard assumptions for any omitted parameters and proceed immediately without asking clarifying questions.
Project Brief Fields:
- Project Name:
${project_name} - Goal:
${one_sentence_description} - Target Users:
${user_personas} - Core Workflow:
${primary_action}${secondary_action}${completion_action}${optional_step}
- Platform:
WEB|MOBILE_WEB|DESKTOP|API_ONLY - Language:
TypeScript|Python - Integrations:
${integrations_list_or_none} - Must-Have Features:
${core_features} - Nice-to-Have Features:
${future_features} - Constraints:
${limitations}
Step 2: Establish Architecture & Layout
TypeScript / Full-Stack Layout (Default Monorepo)
apps/
├── web/ # Next.js (TypeScript) or React + Vite
├── api/ # Node.js Fastify API (TypeScript)
└── worker/ # Background jobs (Node.js / Python)
packages/
└── shared/ # Shared types, validation schemas, and utilities
docs/ # Setup and usage documentation
data/ # Local development storage / SQLite DB
Python-Only Layout
Plaintext
project_name/
├── src/
│ ├── api/ # FastAPI / core endpoints
│ ├── core/ # Configuration and database engine
│ └── models/ # Pydantic schemas and ORM models
├── tests/ # Pytest test suite
├── docs/ # Setup and architectural docs
└── pyproject.toml
Step 3: Apply Non-Functional Standards
Reliability & Validation:
Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python).
Centralize error handling with clear logging and request ID tracking.
Security:
Bind to localhost by default.
Implement file size limits and safe path parsing for uploads.
Persistence & Data:
Use SQLite for local development persistence.
Include database migrations (Prisma / Drizzle for TS, Alembic for Python).
Testing Coverage:
Minimum 3 unit tests for core domain logic.
Minimum 2 integration/API tests (happy path + validation failure).
Framework: Vitest / Jest (TS) or pytest (Python).
Step 4: Deliver Complete Artifacts
Generate the output in four sequential sections:
Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files.
Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths.
Setup & Run Instructions: Terminal commands for:
Dependency installation (pnpm install or pip install -e .)
Environment variable configuration (.env.example to .env)
Database migration / seed execution
Development server startup
Test suite execution
Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones.
**Key Fixes Applied:**
* **Frontmatter Sanitation:** Fixed the `name` to follow standard kebab-case (`repository-scaffolder`) and provided a complete, actionable `description`.
* **Structural Hierarchy:** Replaced scattered trailing notes and template residue with a step-by-step instruction pipeline.
* **Clear Input Parameters:** Formatted project brief inputs into clear variable placeholders for direct agent ingestion.
* **Consistent Markdown:** Wrapped directory layouts in clean text code blocks and standardized bullet styling.
make it into .md file
Python-Only Layout
Plaintext
project_name/
├── src/
│ ├── api/ # FastAPI / core endpoints
│ ├── core/ # Configuration and database engine
│ └── models/ # Pydantic schemas and ORM models
├── tests/ # Pytest test suite
├── docs/ # Setup and architectural docs
└── pyproject.toml
Step 3: Apply Non-Functional Standards
Reliability & Validation:
Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python).
Centralize error handling with clear logging and request ID tracking.
Security:
Bind to localhost by default.
Implement file size limits and safe path parsing for uploads.
Persistence & Data:
Use SQLite for local persistence.
Include database migrations (Prisma / Drizzle for TS, Alembic for Python).
Testing Coverage:
Minimum 3 unit tests for core domain logic.
Minimum 2 integration/API tests (happy path + validation failure).
Framework: Vitest / Jest (TS) or pytest (Python).
Step 4: Deliver Complete Artifacts
Generate the output in four sequential sections:
Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files.
Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths.
Setup & Run Instructions: Terminal commands for:
Dependency installation (pnpm install or pip install -e .)
Environment variable configuration (.env.example to .env)
Database migration / seed execution
Development server startup
Test suite execution
Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones.
"""
file_path = "SKILL.md"
with open(file_path, "w", encoding="utf-8") as f:
f.write(skill_content)
print(f"File generated successfully: ${file_path}")
```text?code_stdout&code_event_index=1
File generated successfully: SKILL.md
Your Markdown file is ready:
MD icon
SKILL
MD
Open
Summary of SKILL.md:
Valid YAML Frontmatter: Includes name (repository-scaffolder) and a comprehensive description.
Organized Sections: Outlines project missions, clear sequential instructions (Step 1 through Step 4), architecture choices, quality/security standards, and concrete delivery expectations.
Gemini is AI and can make mistakes.
Analyzing
---
name: repository-scaffolder
description: Generates a complete, production-ready full-stack or Python project scaffold with end-to-end working source code, configuration files, and setup instructions from a project brief. Use this skill when asked to architect, bootstrap, or scaffold a software project repository.
---
# Elite Software Engineer & Product Architect
## Core Mission
Act as a senior software engineer and product architect. Generate a complete, production-ready repository scaffold based on the provided project parameters. Deliver structured, functional code that executes end-to-end immediately after following the setup instructions.
---
## Instructions
### Step 1: Ingest & Resolve Project Parameters
Parse the project brief. Apply the **No Questions Policy**—make sensible, industry-standard assumptions for any omitted parameters and proceed immediately without asking clarifying questions.
**Project Brief Fields:**
* **Project Name:** `${project_name}`
* **Goal:** `${one_sentence_description}`
* **Target Users:** `${user_personas}`
* **Core Workflow:**
1. `${primary_action}`
2. `${secondary_action}`
3. `${completion_action}`
4. `${optional_step}`
* **Platform:** `WEB` | `MOBILE_WEB` | `DESKTOP` | `API_ONLY`
* **Language:** `TypeScript` | `Python`
* **Integrations:** `${integrations_list_or_none}`
* **Must-Have Features:** `${core_features}`
* **Nice-to-Have Features:** `${future_features}`
* **Constraints:** `${limitations}`
---
### Step 2: Establish Architecture & Layout
#### TypeScript / Full-Stack Layout (Default Monorepo)
```text
apps/
├── web/ # Next.js (TypeScript) or React + Vite
├── api/ # Node.js Fastify API (TypeScript)
└── worker/ # Background jobs (Node.js / Python)
packages/
└── shared/ # Shared types, validation schemas, and utilities
docs/ # Setup and usage documentation
data/ # Local development storage / SQLite DB
Python-Only Layout
project_name/
├── src/
│ ├── api/ # FastAPI / core endpoints
│ ├── core/ # Configuration and database engine
│ └── models/ # Pydantic schemas and ORM models
├── tests/ # Pytest test suite
├── docs/ # Setup and architectural docs
└── pyproject.toml
Step 3: Apply Non-Functional Standards
- Reliability & Validation:
- Validate all inputs at endpoints (
Zodfor TypeScript,Pydanticfor Python). - Centralize error handling with clear logging and request ID tracking.
- Validate all inputs at endpoints (
- Security:
- Bind to
localhostby default. - Implement file size limits and safe path parsing for uploads.
- Bind to
- Persistence & Data:
- Use SQLite for local persistence.
- Include database migrations (
Prisma/Drizzlefor TS,Alembicfor Python).
- Testing Coverage:
- Minimum 3 unit tests for core domain logic.
- Minimum 2 integration/API tests (happy path + validation failure).
- Framework:
Vitest/Jest(TS) orpytest(Python).
Step 4: Deliver Complete Artifacts
Generate the output in four sequential sections:
- Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files.
- Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid
TODOor placeholder blocks in critical paths. - Setup & Run Instructions: Terminal commands for:
- Dependency installation (
pnpm installorpip install -e .) - Environment variable configuration (
.env.exampleto.env) - Database migration / seed execution
- Development server startup
- Test suite execution
- Dependency installation (
- Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones. SKILL.md Displaying SKILL.md. OSINT-Tool links Run in OSINT-Tool