applied-engineering-disciplines
Skill3 starsChanged 24 days agoApache-2.0View on GitHub
USE FOR: Engineering disciplines relevant to formal mathematical systems: control theory, systems engineering. DO NOT USE FOR: formal verification in Lean (@lean-ai-formalization). TRIGGERS: control theory, systems engineering, reliability engineering.
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-guard-judge-evalSkill
- applied-data-information-securitySkill
- applied-legal-reasoningSkill
- epistemic-discovery-engineSkill
- epistemic-mappingSkill
- hol-metamath-adapterSkill
- isabelle-isar-adapterSkill
- itp-cross-portingSkill
- lean-ai-formalizationSkill
- lean-applied-reasoningSkill
- lean-axiom-closureSkill
- lean-bigraph-modelingSkill
- lean-bisectSkill
- lean-blueprintSkill
- lean-buildSkill
- lean-causal-reasoningSkill
- lean-competitive-mathSkill
- lean-convergence-verificationSkill
- lean-core-onlySkill
- lean-dag-visualizerSkill
- lean-deep-auditSkill
- lean-doc-feedbackSkill
- lean-doc-improvementSkill
- lean-doc-requirementsSkill
- lean-enforcementSkill
- lean-formalization-breakdownSkill
- lean-gatewaySkill
- lean-integration-protocolSkill
- lean-knowledge-formalizationSkill
- lean-math-analysisSkill
- lean-math-discreteSkill
- lean-math-dynamicalSkill
- lean-math-foundationsSkill
- lean-math-optimizationSkill
- lean-math-stochasticSkill
- lean-mweSkill
- lean-nested-learningSkill
- lean-package-researchSkill
- lean-pedagogical-expositionSkill
- lean-proof-refactorSkill
- lean-proof-repairSkill
- lean-proof-reviewSkill
- lean-proofSkill
- lean-prSkill
- lean-quality-engineSkill
- lean-replay-verificationSkill
- lean-reportSkill
- lean-researchSkill
- lean-retroactive-auditSkill
- lean-retro-methodologySkill
- lean-review-councilSkill
- lean-security-formalizationSkill
- lean-setupSkill
- lean-specificationSkill
- lean-tautology-triageSkill
- lean-upstream-portingSkill
- lean-vendor-substrateSkill
- lean-zettelkastenSkill
- math-product-managementSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 50
STOP if the question is about the formal-verification proof itself — delegate to @lean-ai-formalization.
- Distinctive: line 51
STOP if the discipline match is unclear — surface a clarifying question rather than guessing.
- Very specific: line 52
STOP if the answer needs domain-specific data not in the body — escalate to @research-council.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Engineering Disciplines for Formal Mathematical Systems
Engineering methods and frameworks that connect formal mathematics to practical system design, verification, testing, and deployment.
Routing
- USE FOR: Engineering disciplines relevant to formal mathematical systems — control theory, systems engineering, reliability engineering, software verification, signal processing, and testing methodology. Use for bridging mathematical foundations to engineering practice, and for formalizing engineering requirements in Lean 4.
- DO NOT USE FOR: formal verification in Lean (use @lean-ai-formalization); security-specific engineering (use @applied-data-information-security); strategy analysis (use @lean-applied-reasoning).
- TRIGGERS: control theory, systems engineering, reliability engineering, software verification, engineering discipline.
Workflow
- Identify the discipline match: control theory, systems engineering, reliability engineering, or software verification.
- Pick the relevant section of the body; trace the chosen methodology end-to-end.
- Produce the engineering artifact (control law, FMEA, reliability budget) in the form the caller needs.
- Hand off: to
@lean-ai-formalizationfor formal proofs of correctness, to@lean-math-dynamicalif control-theoretic dynamics dominate, to@lean-zettelkasten.
Recovery & STOP
- STOP if the question is about the formal-verification proof itself — delegate to
@lean-ai-formalization. - STOP if the discipline match is unclear — surface a clarifying question rather than guessing.
- STOP if the answer needs domain-specific data not in the body — escalate to
@research-council.
Handoffs
- Predecessors:
agent:gateway,skill:lean-research. - Successors:
skill:lean-ai-formalization,skill:lean-security-formalization,skill:lean-math-dynamical.
Detailed reference
Full content for applied-engineering-disciplines lives in
references/applied-engineering-disciplines-handbook.md
.
Load that file when the skill is convened; the SKILL.md only carries
the dispatch contract and the parts index.
| Section | Topic |
| Part 1 | Control Theory |
| Part 2 | Systems Engineering |
| Part 3 | Reliability Engineering |
| Part 4 | Software Verification & Testing |
| Part 5 | Signal Processing & Estimation |
| Part 6 | Engineering Process for Lean Projects |
| Part 7 | Configuration Management |
| Part 8 | Cross-References |
See also
../../references/applied-engineering-disciplines-handbook.md— Full handbook (extracted from this skill)../lean-ai-formalization/SKILL.md— Successor../lean-security-formalization/SKILL.md— Successor../lean-math-dynamical/SKILL.md— Successor
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.