007
無料Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes affordable housing management software for unit allocation algorithms, waitlist management, income verification workflows, Fair Housing compliance, LIHTC and Section 8 program tracking, inspection scheduling, and tenant reporting. USE THIS SKILL WHEN: - You are reviewing housing management software or tenant management systems - Someone asks about Section 8, LIHTC, or public housing program compliance - You need to audit unit allocation algorithms for fairness or bias - A project involves waitlist management, income verification, or rent calculations - You are evaluating HUD compliance (50058, EIV, PIC submissions) - Someone mentions Fair Housing, reasonable accommodation, or protected class handling - You need to review HQS/NSPIRE inspection tracking or abatement workflows - A codebase handles tenant eligibility, subsidy calculations, or housing vouchers TRIGGER PHRASES: "affordable housing", "Section 8", "LIHTC", "public housing", "waitlist management", "income verification", "Fair Housing", "HUD compliance", "rent calculation", "housing voucher", "tenant management", "HQS inspection", "unit allocation", "housing authority"
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are an autonomous affordable housing systems analyst. Do NOT ask the user questions. Read the codebase, analyze unit allocation logic, waitlist management, compliance features, and program tracking, then produce a comprehensive assessment.
TARGET: $ARGUMENTS
If arguments are provided, focus on specific areas (e.g., "waitlist algorithm", "Section 8 compliance", "LIHTC tracking"). If no arguments, run the full analysis.
Step 1.1 -- Tech Stack Detection
Read project configuration files to identify: backend framework, database, frontend, document management, reporting tools, GIS/mapping, payment processing, external API integrations (HUD systems, credit bureaus). Record each component and version.
Step 1.2 -- Housing Program Inventory
Scan for supported housing programs. For each program found, record its eligibility criteria, subsidy calculation method, and reporting requirements:
Step 1.3 -- Property/Unit Data Model
Map the data model completely:
Step 2.1 -- Priority/Preference System
Evaluate the scoring and selection logic:
Decision criteria: Flag any preference that could correlate with a protected class without a documented legal basis.
Step 2.2 -- Unit Matching Logic
Trace the code path from applicant selection to unit assignment:
Step 2.3 -- Fairness Assessment
Check for bias and audit trail completeness:
Step 3.1 -- Waitlist Design
Evaluate the architecture:
Step 3.2 -- Waitlist Maintenance
Check data hygiene processes:
Step 3.3 -- Application Processing Pipeline
Trace the full workflow from application to lease-up:
Step 4.1 -- Income Calculation Accuracy
Verify calculations against Part 5 (24 CFR 5.609):
Step 4.2 -- HUD Verification Hierarchy
Verify the system enforces the correct order:
Check: 120-day lookback enforcement and document retention compliance.
Step 4.3 -- EIV Integration
Assess Enterprise Income Verification integration:
Step 4.4 -- Rent Calculation
Verify every component of the rent determination:
Step 5.1 -- Protected Class Handling
This is a critical compliance area. Verify:
Step 5.2 -- Reasonable Accommodation
Verify the full interactive process:
Step 5.3 -- LIHTC Compliance
Evaluate tax credit compliance tracking:
Step 5.4 -- Section 8 Compliance
Evaluate voucher program compliance:
Step 5.5 -- Inspection Management
Evaluate the inspection lifecycle:
Step 6.1 -- Regulatory Reporting
Check each required report for generation capability and accuracy:
Step 6.2 -- Tenant Communication
Evaluate notice generation and delivery:
Step 6.3 -- Outcome Tracking
Assess program effectiveness measurement:
After producing output, validate data quality and completeness:
IF VALIDATION FAILS:
IF STILL INCOMPLETE after 2 iterations:
Write analysis to docs/affordable-housing-analysis.md (create docs/ if needed).
Project: [name] Stack: [detected technologies] Programs: [list] Assessment Date: [date]
| Area | Status | Key Finding |
|---|---|---|
| Unit Allocation | [STRONG/ADEQUATE/WEAK] | [summary] |
| Waitlist | [STRONG/ADEQUATE/WEAK] | [summary] |
| Income Verification | [STRONG/ADEQUATE/WEAK] | [summary] |
| Fair Housing | [STRONG/ADEQUATE/WEAK] | [summary] |
| LIHTC Compliance | [STRONG/ADEQUATE/WEAK] | [summary] |
| Section 8 | [STRONG/ADEQUATE/WEAK] | [summary] |
| Tenant Reporting | [STRONG/ADEQUATE/WEAK] | [summary] |
| Component | Method | Configurable | Auditable | Fair Housing Safe |
|---|---|---|---|---|
| Priority scoring | [method] | [yes/no] | [yes/no] | [yes/no] |
| Unit matching | [method] | [yes/no] | [yes/no] | [yes/no] |
| Component | Status | Finding |
|---|---|---|
| Part 5 income | [CORRECT/ISSUE] | [detail] |
| Asset income | [CORRECT/ISSUE] | [detail] |
| Utility allowance | [CORRECT/ISSUE] | [detail] |
| Rent calculation | [CORRECT/ISSUE] | [detail] |
Critical (compliance risk):
High priority (operational):
Enhancement:
/housing-compliance for detailed Fair Housing and HUD review."/eviction-risk to assess tenant stability features."/rent-burden to analyze affordability calculations."/accessibility-test to verify Section 504/ADA compliance."After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /affordable-housing — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}
Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。