
sharptoolbox/ontology-driven-dev
Developer toolsThis page was translated automatically. Technical details may differ from the original. View the original
Ontology-driven business system development skills: Three-step method for requirement exploration→ ontology modeling→ application construction, based on seven model ontologies YAML and code-paas technology foundation. Supports WorkBuddy / Claude Code / Codex.
Overview
A set of three steps: "Requirements Exploration → Ontology Modeling → Application Construction." Based on seven model ontologies YAML (M1/M2/M3/M5/M6/M7/MU) and built-in code-Paas technology bases, it enforces manual confirmation at each requirement exploration stage, ultimately producing a runnable browser front-end and backend (BS) system. - : Every function can be traced back to a specific entry in the requirement document; - : Database tables, interfaces, menus, permissions, processes, and rules are all generated by seven models in YAML, eliminating the principle of "one model, one code"; - : The eight stages of requirement exploration, each must be **ed before progressing; - : Built-in code-paas (Flask + SQLite + React/TS monolithic application, including system management, process engine, workbench, ontology registry), can be replicated and expanded; - : The generated application has built-in AI dialogue on the right side (ontology registry injection + tool calls + SSE streaming + read-only SQL security boundary). code-app-example/ Displays the complete implementation results from requirement specifications and the seven-model ontology to runnable systems. The sample business covers sales contract execution management, covering contract registration and hierarchical approval, invoicing approval, collection and write-off, cross-object status linkage, fixed reports, system management, and AI intelligent assistant on the right. The sample includes SQLite test data and default test accounts, allowing you to directly start and verify the complete business chain according to code-app-example/README.md instructions. The AI API Key in the warehouse has been cleared; before using the intelligent assistant, you need to configure OpenAI-compatible large model services in the system interface. This skill** can run fully on tools such as Claude Code, Codex, Cursor, etc. Unique adaptation point: Within the skill, the relative path is rooted in the "folder where the SKILL.md is located," and each tool will automatically parse it. The Skills format of Claude Code is exactly the same as the frontmatter (name / description) of this skill, so the basic ** is sufficient: Claude Code automatically discovers .claude/skills/ /SKILL.md and executes it according to its flow. Codex does not have a native skill registry, but it can load command files from the repository and execute bash in the sandbox:
Overview (machine translated)
A set of ontology-driven business system development skills using a three-step approach of “requirements exploration → ontology modeling → application construction.” Based on the seven model ontologies YAML (M1/M2/M3/M5/M6/M7/MU) and the built-in [T0]] technology base, manual confirmation is required at each requirement exploration stage, ultimately producing a runnable browser front-end and back-end (BS) system that strictly aligns requirements documents, ontology models, and code**.
English version → README_EN.md
1. What can this skill do?
Turn a business requirement (a sentence or a description) into a runnable management system, and guarantee:
- Requirement Traceability: Each feature can be traced back to a specific entry in the requirements document;
- Model as Semantic Source: Database tables, interfaces, menus, permissions, processes, and rules are all generated by seven models using YAML, eliminating the principle of “one model, one code”;
- Manual access control cannot be skipped: The 8 stages of requirement exploration, each must be paused and confirmed by the person before progressing.
- Out-of-the-box tech foundation: Built-in
code-paas(Flask + SQLite + React/TS monolithic application, including system management, process engine, workbench, ontbook registry), can be copied and expanded; - Forced AI Dialog Box: The generated application comes with AI dialogue on the right side (ontology registry injection + tool call + SSE streaming + read-only SQL security boundary).
2. Include content
Complete application example
code-app-example/ Presented the complete implementation results from requirement specifications and the seven-model ontology to the runnable system. The sample business is sales contract execution management, covering contract registration and hierarchical approval, invoicing approval, collection and write-off, cross-object status linkage, fixed reports, system management, and the AI intelligent assistant on the right.
The sample includes SQLite test data and default test accounts, allowing you to directly start and verify the complete business chain according to the instructions in code-app-example/README.md. The AI API Key in the warehouse has been cleared. Before using the intelligent assistant, you need to configure OpenAI-compatible large model services in the system interface.
3. Installation (Mainstream Tools)
This skill does not rely on any WorkBuddy proprietary mechanisms and can fully run on tools such as Claude Code, Codex, Cursor, etc. Unique adaptation point: Within skills, the relative path is rooted in the folder where the SKILL.md is located, and each tool will automatically parse it.
1. WorkBuddy
You can simply say the trigger in the WorkBuddy conversation (see Section 5).
2. Claude Code
The Skills format of Claude Code is exactly the same as the frontmatter (name / description) of this skill, so basically, just copy directly:
Claude Code automatically discovers .claude/skills/ /SKILL.md and executes it according to its flow.
3. Codex
This page was translated automatically. Technical details may differ from the original.
Recommended Tools
Try a different keyword or remove a filter.
Install
npx skillfish add sharptoolbox/ontology-driven-dev