메뉴
Vulnerability disclosure, responsible reporting, compliance, security contacts for CampusOS. Use when setting up security reporting, creating vulnerability disclosure policy, or managing incident response.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | security-policy |
| description | Vulnerability disclosure, responsible reporting, compliance, security contacts for CampusOS. Use when setting up security reporting, creating vulnerability disclosure policy, or managing incident response. |
# Security Policy
## Reporting a Vulnerability
**Do not open public issues for security vulnerabilities.**
Email: security@campusos.org
Include:
- Description of vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if available)
## Response Timeline
- Acknowledgement: Within 24 hours
- Initial assessment: Within 7 days
- Fix or mitigation: Within 30 days
- Public disclosure: After fix published
| Severity | Definition | Fix Timeline |
|---|---|---|
| Critical | Data breach, auth bypass | 72 hours |
| High | DoS, privilege escalation | 7 days |
| Medium | Info disclosure, authz bypass | 14 days |
| Low | Low-impact issues | 30 days |
| Framework | Relevance |
|---|---|
| GDPR | If serving EU users |
| FERPA | Education records |
| SOC 2 | Enterprise customers |
| CCPA | California users |
pnpm audit # Dependency vulnerabilities (weekly)
pnpm exec snyk code test # Static analysis
pnpm audit # Security audit
git log -p | grep -i "secret" # Check for exposed secrets
Build React components in Next.js using CampusOS patterns. Use when implementing UI components, working with the App Router, styling with Tailwind CSS v4, or managing forms with react-hook-form and Zod.
Comprehensive frontend development hub — UI/UX design, React/Next.js patterns, Tailwind CSS v4, shadcn/ui components, Three.js 3D graphics, creative web experiences, data visualization, diagramming, Figma integration, accessibility, game development, scroll animations, and design systems. Use for ANY frontend task: building components, designing interfaces, styling, theming, animations, charts, responsive layouts, mobile design, or implementing design patterns.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
Generate commit titles and descriptions from uncommitted changes. Use when the user asks to generate a commit message, wants help writing a commit, or says 'commit', 'commit message', 'what should I commit', or similar.
Generate PR titles and descriptions from commit history. Use when the user asks to generate a PR description, wants help writing a pull request, provides commit titles/messages, or says 'PR', 'pull request', 'PR description', or similar.