notque/vexjoy-agent / skills/programming/programming
programming
FlaggedLanguage rules, workflows, and tooling: Go, Python, Rust, Kotlin, Swift, PHP, TypeScript type checks and debugging, OpenStack Python, MCP local-docs servers, Node.js backend APIs.
references/python-openstack/output-format.md
View on GitHub# OpenStack Output Format
OpenStack work uses the **Implementation Schema**.
**Phase 1: ANALYZE** — Identify OpenStack components, Oslo requirements, Tempest coverage plan.
**Phase 2: DESIGN** — Service architecture (WSGI, RPC, DB models), oslo.config options, RPC versioning strategy.
**Phase 3: IMPLEMENT** — Service with Oslo integration, Alembic migrations, Tempest tests, hacking compliance.
**Phase 4: VALIDATE** — `tox -e py3`, `tox -e tempest`, `tox -e pep8`, i18n compliance check.
**Final Output**:
```
═══════════════════════════════════════════════════════════════
OPENSTACK IMPLEMENTATION COMPLETE
═══════════════════════════════════════════════════════════════
Service Components:
- WSGI application (Paste Deploy)
- Oslo.config integration
- Oslo.messaging RPC handlers
- Database models + Alembic migrations
- Policy enforcement (oslo.policy)
Testing:
- Unit tests: >80% coverage
- Tempest integration tests
- Hacking compliance: ✓
Verification:
- tox -e pep8: PASS
- tox -e py3: PASS
- tox -e tempest: PASS
- i18n compliance: ✓
Next Steps:
- DevStack integration: Create devstack/plugin.sh
- Documentation: Update api-ref/source/
- Gerrit review: git review -t topic-name
═══════════════════════════════════════════════════════════════
```
## Capabilities & Limitations
### In Scope
- Implement OpenStack services with WSGI, oslo.config, oslo.messaging RPC, oslo.db, oslo.policy
- Develop Neutron ML2 drivers with mechanism/type drivers, RPC callbacks, Tempest tests
- Create Tempest tests with service clients, scenario tests, API validation, resource cleanup
- Integrate Oslo libraries (config, log, messaging, db)
- Implement Alembic migrations with contract/expand pattern for zero-downtime upgrades
- Handle RPC versioning with version caps and negotiation
### Out of Scope
- **Deploy production OpenStack**: Requires DevOps specialist (Kolla/Ansible)
- **Tune OpenStack performance**: Requires infrastructure specialist
- **Design cloud architectures**: Requires cloud architect
- **Fix upstream core bugs**: Contribute via Gerrit
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 197k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |