القائمة
Security-focused TAPPS workflow: playbook, library docs, security scan, and CVE check. Use when implementing auth, secrets, input validation, or pre-release security passes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Persistent cross-session memory + knowledge graph for AI coding agents. Use when you need to recall prior decisions before making a non-trivial choice, save the rationale behind a decision so it survives the session, share findings across agents in a project (Hive), or record an experience event / KG triple. Talk to the deployed brain at http://127.0.0.1:8080/mcp/ via MCP tools — never via raw psycopg.
Frontend work flow combining UX playbook and standard finish pipeline. Use when the task is primarily UI/UX implementation or accessibility.
Write a structured cross-session handoff and close the TAPPS session lifecycle so the next chat can continue without a long paste. Use when ending a session, handing off to a fresh chat, or the user says hand off, save session state, or continue next time.
Frontend work flow combining UX playbook and standard finish pipeline. Use when the task is primarily UI/UX implementation or accessibility.
Write a structured cross-session handoff and close the TAPPS session lifecycle so the next chat can continue without a long paste. Use when ending a session, handing off to a fresh chat, or the user says hand off, save session state, or continue next time.
Persistent cross-session memory + knowledge graph for AI coding agents. Use when you need to recall prior decisions before making a non-trivial choice, save the rationale behind a decision so it survives the session, share findings across agents in a project (Hive), or record an experience event / KG triple. Talk to the deployed brain at http://127.0.0.1:8080/mcp/ via MCP tools — never via raw psycopg.
| name | tapps-domain-security |
| user-invocable | true |
| model | claude-sonnet-4-6 |
| description | Security-focused TAPPS workflow: playbook, library docs, security scan, and CVE check. Use when implementing auth, secrets, input validation, or pre-release security passes. |
| allowed-tools | mcp__nlt-build__tapps_session_start mcp__nlt-build__tapps_domain_playbook mcp__nlt-build__tapps_lookup_docs mcp__nlt-build__tapps_quick_check mcp__nlt-build__tapps_validate_changed mcp__nlt-build__tapps_checklist mcp__nlt-build__tapps_security_scan mcp__nlt-build__tapps_dependency_scan |
| argument-hint | [file-path or scope] |
Domain playbook workflow — same quality gate as the standard TAPPS pipeline.
tapps_session_start() if not already called this session.tapps_domain_playbook(domain="security") (or read bundled checklist from the response). Follow its workflow and checklist.lookup_hints, call tapps_lookup_docs(library=..., topic=...) before using those APIs.recommended_tools on changed files in scope.tapps_quick_check(file_path=...).
4b. Run tapps_security_scan on sensitive changed files.
4c. Run tapps_dependency_scan when lockfiles or dependencies changed./tapps-finish-task with the task_type=security. Do not declare done without validate + checklist.