diff --git a/.agents/rules/blog-system.md b/.agents/rules/blog-system.md index 5e64605..d27d847 100644 --- a/.agents/rules/blog-system.md +++ b/.agents/rules/blog-system.md @@ -65,6 +65,7 @@ excerpt: "Single paragraph summary" readingTime: "X MIN READ" draft: false + hidden: false # optional: true unlists post from public feeds/lists, accessible via direct link only ``` 2. **Obsidian Normalization:** - Wikilinks `[[slug]]` or `[[slug|Label]]` must be transformed into standard web URLs (`/posts/slug/`). diff --git a/.agents/skills/obsidian-sync/SKILL.md b/.agents/skills/obsidian-sync/SKILL.md index 783ca4a..4d83cea 100644 --- a/.agents/skills/obsidian-sync/SKILL.md +++ b/.agents/skills/obsidian-sync/SKILL.md @@ -61,7 +61,8 @@ This skill guides the agent in implementing the custom Obsidian plugin and serve ## 3. Obsidian Markdown Normalization Rules 1. **Frontmatter Invariants:** - - Must contain `title`, `date`, `tags` (array), and optional `excerpt`, `readingTime`, `draft`. + - Must contain `title`, `date`, `tags` (array), and optional `excerpt`, `readingTime`, `draft`, `hidden`. + 2. **Wikilinks Translation:** - `[[article-slug]]` $\rightarrow$ `[article-slug](/posts/article-slug/)` - `[[article-slug|Custom Label]]` $\rightarrow$ `[Custom Label](/posts/article-slug/)` diff --git a/.agents/skills/standards-verification/SKILL.md b/.agents/skills/standards-verification/SKILL.md new file mode 100644 index 0000000..2fdd32e --- /dev/null +++ b/.agents/skills/standards-verification/SKILL.md @@ -0,0 +1,94 @@ +--- +name: standards-verification +description: >- + Use this skill sparingly when a new major function or feature has been implemented, when the user explicitly asks to verify standards, or as a debugging tool to analyze code issues. Targets only modified or relevant files via git status/diff and evaluates them against the project standards document. +--- + +# Standards Verification Skill + +This skill performs targeted architectural and stylistic compliance verification for new or modified code in this repository. + +> [!IMPORTANT] +> **Invocation Policy:** Call this skill **sparingly and only when needed**. +> **Valid Triggers:** +> 1. A new major function or architectural feature has been implemented. +> 2. The user asks to call it or requests standards verification. +> 3. An error, test failure, or regression has occurred, and you are using this skill as a debugging tool to determine where the code diverges from project standards. + + +--- + +## 1. Targeted Inspection Scope (Not the Whole Codebase) + +Do **NOT** scan or audit the whole codebase unless specifically requested by the user or strictly necessary for whole-system refactors. + +Instead, narrow the scope to targeted sections using Git: + +1. **Check Modified Files:** + ```bash + git status -s + ``` +2. **Inspect Exact Changes:** + ```bash + git diff HEAD + ``` + Or for staged changes: + ```bash + git diff --staged + ``` +3. **Identify Changed Sections:** + Focus only on the files, functions, templates, or styles touched in the current task. + +--- + +## 2. Standards Evaluation Workflow + +To verify compliance, read the dedicated project standards document: +- Authoritative document: [`.agents/standards.md`](file:///home/venus/code/blog/.agents/standards.md) (or local skill reference: [`references/standards.md`](file:///home/venus/code/blog/.agents/skills/standards-verification/references/standards.md)). + +Evaluate the targeted changes against the core standard pillars: + +1. **Design System & CSS Rules:** + - Are any anti-patterns present? Check for `backdrop-filter`, `box-shadow`, `text-shadow` (other than `none`), gradients, or transitions with delays/curves. + - Are border radii strictly bounded between `0px` and `4px`? + - Are colors utilizing CSS custom properties from `tokens.css`? + - Is styling modularized without inline `