chore(claude): sync rules and project settings from rulesync

Made-with: Cursor

Author: codekiln

.claude/rules/logseq-forum-post.md

@@ -1,6 +1,6 @@
 # Formatting Forum Posts in Logseq
 
-This rule defines the standard format for importing and structuring forum posts in Logseq, including posts from Cursor, Reddit, Stack Overflow, and other forums. This rule works in conjunction with the logseq-person rule for handling person references.
+This rule defines the standard format for importing and structuring forum posts in Logseq, including posts from Cursor, Reddit, Stack Overflow, and other forums. For person hubs, use the **logseq-person** router and `[[Logseq/Entity/person]]` (see **logseq-entity** skill).
 
 ### ⚠️ CRITICAL: DO NOT MODIFY FRONTMATTER TAGS ⚠️
 
@@ -55,7 +55,7 @@ When referencing users in forum posts:
      - They have a substantial online presence
 
 2. **Person References**
-   - Follow the logseq-person rule for creating/updating person references
+   - Follow `[[Logseq/Entity/person]]` and the **logseq-person** router for creating/updating person hub references
    - Only create new person pages for significant contributors
    - Update existing person pages if found
    - Include:

.claude/rules/logseq-naming-conventions.md

@@ -20,7 +20,7 @@ This is an extension to the logseq-flavored-markdown rule for maintaining consis
    - Use singular form: `[[Project]]` not `[[Projects]]`
 
 2. **Aliases**
-   - Add plural form as an alias in the page's frontmatter
+   - Add a plural or contextual form as an alias in the page's frontmatter when you want that link text to resolve to the singular canonical page.
    - Example:
      ```markdown
      ---
@@ -29,8 +29,8 @@ This is an extension to the logseq-flavored-markdown rule for maintaining consis
      ```
 
 3. **References**
-   - Use plural form in references: `[[Related Posts]]`
-   - The alias will resolve to the singular page name
+   - Use the alias link text in references when you want the plural or contextual surface form: `[[Related Posts]]`
+   - The alias resolves to the singular page name
    - This maintains consistency while allowing for sub-namespaces
 
 ### Benefits
@@ -42,16 +42,15 @@ This is an extension to the logseq-flavored-markdown rule for maintaining consis
 ### Examples
 
 <CORRECT_✅>
-- [[Person/John Smith]] (singular page name)
-  - alias:: [[People/John Smith]]
+- [[Person/John Smith]] (singular person hub; see `[[Logseq/Entity/person]]` — do not use a parallel `[[People/...]]` alias)
 - [[Project/Cursor]] (singular page name)
   - alias:: [[Projects/Cursor]]
 - [[Related/Post]] (singular page name)
   - alias:: [[Related Posts]]
 </CORRECT_✅>
 
 <INCORRECT_❌>
-- [[People/John Smith]] (plural in page name)
+- [[People/John Smith]] (plural in page name — not used for persons in this garden)
 - [[Projects/Cursor]] (plural in page name)
 - [[Related Topics]] (plural in page name)
 </INCORRECT_❌>

.claude/rules/logseq-person.md

@@ -2,65 +2,11 @@
 paths:
   - '{journals,pages}/*.md'
 ---
-# How a Person is tracked in this Logseq knowledge garden
-This is an extension to the logseq-flavored-markdown rule for recording information about a person.
-
-A person entry is a logseq page where the page title matches one of the following patterns:
-- [[People/Full Name]] (corresponds to `pages/People___Full Name.md`)
-- [[Person/Full Name]] (corresponds to `pages/Person___Full Name.md`)
-- [[<AnyNamespace>/People/Full Name]] (e.g., `pages/HU___People___Full Name.md`)
-- [[<AnyNamespace>/Person/Full Name]] (e.g., `pages/AI___Person___Full Name.md`)
-
-### When to Create a Person Page
-
-Person pages should only be created for individuals who meet one or more of these criteria:
-- Known across multiple platforms (e.g., GitHub, Twitter, Stack Overflow)
-- Have a confirmed real identity
-- Are significant contributors or maintainers
-- Have a substantial online presence
-- Are key figures in their field
-
-For other users, use site-specific namespaces:
-- `[[CursorAI/Forum/User/Username]]` for Cursor Forum users
-- `[[Reddit/User/Username]]` for Reddit users
-- `[[StackOverflow/User/Username]]` for Stack Overflow users
-- `[[ForumName/User/Username]]` for other forum users
-
-### Creating a Person Page
-
-If you are asked to make an entry for a person, you should:
-
-1. **Search First - CRITICAL for Deduplication**
-   - **Before creating or referencing a person page, you MUST search thoroughly:**
-     - Search in `pages/People___*.md`, `pages/Person___*.md`, and in any file matching `pages/**___People___*.md` or `pages/**___Person___*.md`
-     - Search by full name, partial name, username/handle, and common variations
-     - Check aliases in existing person pages (read the `alias::` frontmatter)
-     - Look for name variations (e.g., "Shawn Wang" vs "Shawn @swyx Wang" vs "@swyx")
-   - **If a person page already exists:**
-     - **DO NOT create a new page** - update the existing entry instead
-     - **When referencing the person, use the canonical page name** (the actual filename), NOT aliases
-     - Example: If page is `Person___Shawn @swyx Wang.md` with alias `[[Person/Shawn Wang]]`, reference it as `[[Person/Shawn @swyx Wang]]`, not `[[Person/Shawn Wang]]`
-   - **A single person should NEVER have more than one person page** - this is a critical deduplication rule
-
-2. **Verify Significance**
-   - Confirm the person meets the criteria for a person page
-   - If not, use the appropriate site-specific namespace instead
-
-3. **Create/Update Page**
-   - If a new person page is needed, create it under `[[Person/Full Name]]` by default
-   - If the person is referenced in other contexts/namespaces (e.g., `[[People/Full Name]]`, `[[HU/Person/Full Name]]`), add aliases in the frontmatter to those contexts using `alias::` (not `aliases::`)
-   - Look up the person on the internet
-   - Create a person page for them if they meet the criteria
-   - Link the person and a bit of their bio in their page
-   - If possible add an image link
-   - Include relevant external links (GitHub, LinkedIn, etc.)
-
-4. **Referencing Existing Person Pages**
-   - **Always use the canonical page name** when creating references in content
-   - The canonical name is the actual page filename (e.g., `Person___Shawn @swyx Wang.md` → `[[Person/Shawn @swyx Wang]]`)
-   - **Do NOT use aliases** when referencing - aliases are for backward compatibility, not for new references
-   - If unsure of the canonical name, search for the person page first and use the exact page title
-
-5. **Journal Entry**
-   - If the person page is new, make an entry in today's journal page that links to that person
-   - Use the canonical page name in the journal entry
+# Person entities (router)
+
+- **Authoritative SOP:** `[[Logseq/Entity/person]]` — how we recognize person **hub** pages (`[[Person/Full Name]]` only), namespace vs entity type, `logseq-entity::`, aliases, dedup, and SCM child pages.
+- **Workflow:** Use the **logseq-entity** skill: read `[[Logseq/Entity]]` and the person type page, dedupe before creating, then create or update pages per that SOP (fallback: `.rulesync/config/logseq-entity.md` section **person**).
+- **This rule file** stays short; do not reintroduce legacy `[[People/...]]` title or alias patterns here or in new pages.
+- **Search before create:** `rg` / glob on `pages/Person___*.md`, name variants, and `alias::` lines; one hub per human; canonical link text must match the real page title.
+- **Tags:** Never modify, add, or remove **`tags::`** on existing pages unless a separate human instruction explicitly overrides garden tagging rules.
+- **Journal:** When filing a new person hub from a session, follow `logseq-journal-updates` (link under `[[Filed]]`, etc.).

.claude/rules/logseq-scm-project-link-style.md

@@ -33,11 +33,11 @@ Do not introduce or keep generic SCM path styles such as:
 
 1. When adding or editing GitHub/GitLab project references, rewrite them to the canonical person-first namespace.
 2. If the person page exists, use that exact canonical person name in links.
-3. If the person page does not exist and the task requires creating references, create/update the person page first using existing person-page conventions.
+3. If the person page does not exist and the task requires creating references, create/update the person **hub** first per `[[Logseq/Entity/person]]` (and the **logseq-entity** skill).
 4. For legacy content updates, normalize existing non-canonical SCM links to this style.
 
 ## Related
 
 - command: `logseq-normalize-scm-project-links` - Normalize GitHub/GitLab project links in a file or across changed files
-- rule: `logseq-person` - Person page deduplication and canonical person naming
+- rule: `logseq-person` (router) — see `[[Logseq/Entity/person]]` for person hub dedup and naming
 - rule: `logseq-page-naming-reference` - Namespace/file naming rules

.claude/settings.json

@@ -1,5 +1,20 @@
 {
   "permissions": {
-    "deny": []
+    "deny": [
+      "Read(credentials/)"
+    ]
+  },
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "$CLAUDE_PROJECT_DIR/.rulesync/hooks/format.sh"
+          }
+        ]
+      }
+    ]
   }
 }