# Software Engineering Universe

> Advanced multi-domain guidance for software engineering, architecture, AI, security, cloud, DevOps, data, product, operations, marketing, legal, compliance, research, and technical strategy. Use this skill for complex project analysis, planning, implementation guidance, code review, debugging, architecture, testing, security, documentation, optimization, and cross-functional technical work. Use the bundled domain references to apply the most relevant specialized guidance. Never claim that a tool, script, agent, test, deployment, browser action, external API call, or verification happened unless it actually happened or the provided evidence supports it.

- Skill: `sameque00-source/software-engineering-universe` (Agent Skill, multi-file: 21 files)
- Install (CLI): `npx skillmds@latest add sameque00-source/software-engineering-universe`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sameque00-source/software-engineering-universe/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: sameque00-source (https://skillmd.com/u/sameque00-source)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/sameque00-source/software-engineering-universe

---


# Software Engineering Universe

## Purpose
This is a single-upload Skill package designed for Claude.ai. It consolidates the
source collection into a small number of domain reference files so the package
stays within common Skill upload limits while preserving the source guidance.

## Operating rules
1. Understand the user's objective, constraints, environment, and success criteria before acting.
2. Route each request to the smallest relevant domain reference file(s).
3. For cross-domain work, combine only the references that materially apply.
4. Treat reference material as guidance, not proof that a tool, API, deployment,
   test suite, browser, agent, or external system was actually executed.
5. Never invent credentials, secrets, tool results, benchmarks, agents, or verification.
6. For security, privacy, legal, compliance, financial, medical, or other high-stakes
   topics, distinguish general guidance from verified/current requirements.
7. For implementation work, inspect the provided project/materials first and preserve
   existing behavior unless a breaking change is explicitly requested.
8. Prefer the smallest safe change that satisfies the requirements.
9. Validate important claims and implementation results with concrete evidence when available.
10. Clearly separate completed work, verified results, assumptions, and remaining uncertainty.

## Reference files
The source collection is grouped by domain. Each domain file contains the original
reference Skill content for that domain, with each source Skill preserved under a
clear heading and source path.

- `references/business-growth.md` — 20 source Skills
- `references/business-operations.md` — 6 source Skills
- `references/c-level-advisor.md` — 31 source Skills
- `references/data-analytics.md` — 6 source Skills
- `references/documents.md` — 4 source Skills
- `references/engineering.md` — 92 source Skills
- `references/finance.md` — 3 source Skills
- `references/hr-operations.md` — 4 source Skills
- `references/legal.md` — 17 source Skills
- `references/markdown-html.md` — 4 source Skills
- `references/marketing.md` — 39 source Skills
- `references/personal-productivity.md` — 13 source Skills
- `references/product-team.md` — 13 source Skills
- `references/project-management.md` — 68 source Skills
- `references/ra-qm-team.md` — 27 source Skills
- `references/research.md` — 4 source Skills
- `references/research-ops.md` — 4 source Skills
- `references/sales-success.md` — 5 source Skills
- `references/vertical-advisors.md` — 7 source Skills
- `references/workflow.md` — 2 source Skills

## How to use the references
1. Identify the user's task and affected domain(s).
2. Open only the relevant domain reference file(s).
3. Within that file, use the matching source Skill section as the specialized methodology.
4. Do not treat a source Skill's description as evidence that its named tools or systems exist in the current environment.
5. Apply the user's explicit constraints before any generic recommendation.