ST

sachin0034-tech/dev-os

开发工具

本页由 AI 翻译,技术细节请以原文为准。 查看原文

8 stars 质量 46 趋势 11

sachin0034-tech/dev-os 是从 https://github.com/sachin0034-tech/dev-os. 导入的特工技能候选人

概览

sachin0034-tech/dev-os 是从 https://github.com/sachin0034-tech/dev-os. 导入的特工技能候选人

概述(AI 翻译)

一个结构化的AI辅助开发操作系统,用于构建生产准备应用——从构想到产品部署,采用阶段门槛工作流程,并通过Claude Code技能强制执行。


这是什么

dev-os 是一个 Claude 代码项目,提供可重复的分阶段工作流程,用于构建全栈网页应用。每个阶段都有专门的技能,Claude 在调用时执行。在上一个阶段获得批准之前,任何阶段都不会开始。

当前的应用目标是ContractIQ——一个用于保密协议和MSA分析的企业AI合同审查平台。


文件夹结构

docs/engineering/、docs/specs/、docs/security/和[.env.example]下的文件和文件夹是生成输出——它们在构建流程中创建,直到各自阶段运行时才会存在。


构建工作流程

每个阶段必须完成并获批,才能进入下一阶段。

阶段 技能 输入 输出
1 — 工程计划 /engineering-planner PRD docs/engineering/engineering-doc.md + docs/engineering/implementation-specs.md
2 — 实现规格 /implementation-specs 第一阶段文档 'docs/specs/*.

本页由 AI 翻译,技术细节请以原文为准。

README

以下为原文 README 节选,完整内容请查看原文。

dev-os

A structured AI-assisted development operating system for building production-ready apps — from idea to deployed product using a stage-gated workflow enforced through Claude Code skills.


What This Is

dev-os is a Claude Code project that provides a repeatable, stage-by-stage workflow for building full-stack web applications. Each stage has a dedicated skill that Claude runs when invoked. No stage begins until the previous one is approved.

The current application target is ContractIQ — an enterprise AI contract review platform for NDA and MSA analysis.


Folder Structure

dev-os/
├── CLAUDE.md                     # Project instructions & stage-gated workflow rules
├── docs/
│   ├── design.md                 # Brand design system (colors, typography, spacing, components)
│   ├── ContractIQ_PRD.md         # Product Requirements Document for ContractIQ
├── skills/                       # Claude Code custom skills (slash commands)
│   ├── engineering-planner/
│   │   └── SKILL.md              # Stage 1: PRD → engineering docs
│   ├── implementation-specs/
│   │   └── SKILL.md              # Stage 2: Engineering docs → granular specs + SQL
│   ├── security-foundation/
│   │   └── SKILL.md              # Stage 3: Specs → security controls + RLS policies
│   ├── frontend-setup/
│   │   └── SKILL.md              # Stage 4: Scaffold Next.js 14 App Router project
│   └── design-system/
│       └── SKILL.md              # Applied during all frontend work — enforces design.md

Files and folders under docs/engineering/, docs/specs/, docs/security/, and .env.example are generated outputs — they are created during the build workflow and do not exist until their respective stage runs.


The Build Workflow

Each stage must be completed and approved before the next begins.

Stage Skill Input Output
1 — Engineering Plan /engineering-planner PRD docs/engineering/engineering-doc.md + docs/engineering/implementation-specs.md
2 — Implementation Specs /implementation-specs Stage 1 docs docs/specs/*.md + docs/specs/supabase-schema.sql + .env.example
3 — Security Foundation /security-foundation Stages 1–2 docs docs/security/security-plan.md + supabase/rls-policies.sql + src/lib/security/
4 — Frontend Setup /frontend-setup Stages 2–3 docs Scaffolded Next.js 14 app
5 — Feature Implementation (manual, one feature at a time) docs/specs/*.md Feature code

Skills

Skills live in skills//SKILL.md and are invoked as slash commands in Claude Code.

/engineering-planner

Transforms a PRD into two engineering documents. Asks clarifying questions (auth strategy, DB, LLM provider, user roles) before generating anything. Output is the authoritative reference for all downstream stages.

/implementation-specs

在 GitHub 查看完整 README

推荐工具

换一个关键词,或者移除筛选条件。

安装

npx skillfish add sachin0034-tech/dev-os
新手?先看 mcpskill.org 教程 →