菜单
Content strategy and audience-aware guidelines for the Envilder website. Use when writing page copy, structuring documentation sections, or crafting messaging that targets both developers and technical leaders (CTOs). Provides product context and selling points per audience.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | website-content-strategy |
| description | Content strategy and audience-aware guidelines for the Envilder website. Use when writing page copy, structuring documentation sections, or crafting messaging that targets both developers and technical leaders (CTOs). Provides product context and selling points per audience. |
Guidelines for creating content that communicates Envilder's value to two distinct audiences: developers and CTOs / technical leaders.
Envilder is a TypeScript CLI tool and GitHub Action that securely centralizes environment variables from AWS SSM Parameter Store or Azure Key Vault.
.env files, git repos, or CI logs;
fetched from cloud vault at runtimeenvilder.json = single source of truth for all
environments (dev, staging, production)Developers want to know how it works and how to use it quickly.
envilder.json examples--exec mode, push mode, and GitHub Action inputsTerminalMockup.astro) for live demos.env workflows: zero migration cost--exec mode to inject secrets without writing filesenvilder.jsonLeaders want to know business impact and risk reduction.
Use before/after format to show improvement:
| Without Envilder | With Envilder |
|------------------|---------------|
| Copy secrets manually from AWS console | `npx envilder --map=map.json` |
| 12 steps to onboard a new developer | 1 command |
| Secrets scattered in .env files | Single source of truth in SSM |
For developer-facing content, use TerminalMockup.astro to show real
CLI output. More compelling than static code blocks.
Use .pixel-card with emoji icons for feature grids. Group by audience
concern (security, DX, compliance, multi-cloud).
website-i18n skill)Workflow for investigating and reproducing bugs before fixing via TDD. Use when a bug report or GitHub issue is received. Covers issue fetching, root cause analysis, reproduction planning, and handoff to TDD cycle.
CRAP score quality gate for code complexity and test coverage. Use when reviewing methods for complexity risk, deciding whether to split methods, or determining minimum test coverage requirements.
Code smell detection and safe incremental refactoring patterns. Use when improving code structure, reducing technical debt, or cleaning up after a TDD cycle. Covers SOLID principles, smell catalog, and the propose-apply workflow.
Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity. Use when reviewing PRs, commits, or local changes. Includes severity model and output format.
Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions. Use when making design choices, reviewing proposals for consistency with prior decisions, or onboarding to understand why specific tools or patterns were chosen. Covers test tooling, SDK architecture, code quality, and acceptance test infrastructure.
Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning. Use when creating commits, pull requests, or managing Git workflow.