Thanks for contributing to the Secure Design Practicum.
- Improve guides, prompts, and templates
- Fix workflow bugs or documentation gaps
- Add generalized examples that help teams reason about security earlier
- Keep examples generic and reusable across organizations
- Do not add real secrets, credentials, customer data, or internal-only URLs
- Prefer practical guidance over policy-heavy prose
- Update related docs when behavior changes
- Describe the problem and the intended outcome
- Include sample output or screenshots when changing developer-facing workflows
- Call out any new secrets, permissions, or third-party integrations
- Keep changes scoped and easy to review
If a change affects authentication, authorization, secrets handling, workflow permissions, or external integrations, note that clearly in the pull request so reviewers can give it the right level of attention.