feat: add new skills for coding standards, continuous learning, detail layout, form layout, project guidelines, security review, and verification loop

- Introduced coding standards for TypeScript and React in SKILL.md.
- Added continuous learning skill with configuration and evaluation scripts.
- Created detail layout guidelines for read-only pages.
- Established form layout rules for data-entry forms.
- Documented project guidelines for the frontend monorepo.
- Implemented security review checklist for frontend/Electron applications.
- Developed a verification loop skill for comprehensive session checks.

This commit enhances the skill set available for developers, ensuring adherence to best practices and improving code quality.
This commit is contained in:
shancheas
2026-08-25 16:58:10 +07:00
parent e0d55dae13
commit ff6814d038
69 changed files with 5757 additions and 0 deletions
+50
View File
@@ -0,0 +1,50 @@
---
description: Cursor hooks system, auto-accept permissions, and TodoWrite practices
alwaysApply: true
---
# Hooks System
Project hooks live in `.cursor/hooks.json` (schema version 1) and scripts under `.cursor/hooks/` and `.cursor/scripts/hooks/`.
## Hook Events
- **sessionStart / sessionEnd**: Load and persist session context
- **preCompact**: Save state before context compaction
- **afterFileEdit**: Suggest strategic compact after edits
- **beforeShellExecution**: Gate long-running servers and `git push`
## Current Project Hooks
### sessionStart
- Load previous session files from `.cursor/sessions/`
- Detect package manager
- Report learned skills in `.agents/skills/learned/`
### sessionEnd
- Persist session state
- Evaluate the session for extractable patterns
### preCompact
- Log compaction and append a note to the active session file
### afterFileEdit
- Suggest manual compaction after many edits
### beforeShellExecution
- Ask before running dev servers outside tmux
- Ask before `git push`
## Auto-Accept Permissions
Use with caution:
- Enable for trusted, well-defined plans
- Disable for exploratory work
- Never skip permissions for git push, installs, or production commands
## TodoWrite Best Practices
Use TodoWrite to:
- Track progress on multi-step tasks
- Verify understanding of instructions
- Show granular implementation steps