dsh-aris-panel 0.1.0

package/skills/skills-codex/pixel-art/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: "pixel-art"
+description: "Generate pixel art SVG illustrations for READMEs, docs, or slides. Use when user says \"\u753b\u50cf\u7d20\u56fe\", \"pixel art\", \"make an SVG illustration\", \"README hero image\", or wants a cute visual."
+---
+
+# Pixel Art SVG Generator
+
+Create a pixel art SVG illustration: $ARGUMENTS
+
+## Design Principles
+
+### Pixel Grid
+- Each "pixel" is a `<rect>` with width/height of 7px
+- Grid spacing: 7px (no gaps between pixels)
+- Characters are typically 8-10 pixels wide, 8-12 pixels tall
+- Use `<g transform="translate(x,y)">` to position and reuse character groups
+
+### Color Palette
+Keep it simple — 3-5 colors per character:
+- **Skin**: `#FFDAB9` (light), `#E8967A` / `#D4956A` (blush/shadow)
+- **Eyes**: `#333`
+- **Hair**: `#8B5E3C` (brown), `#2C2C2C` (black), `#FFD700` (blonde), `#C0392B` (red)
+- **Clothes**: use project's brand color (e.g. `#4A9EDA` for blue, `#74AA63` for green)
+- **Shoes/pants**: `#444`
+- **Accessories**: `#555` (glasses frames), `#FFD700` (crown)
+
+### Character Template (7px grid)
+```
+Row 0 (hair top):     4 pixels centered
+Row 1 (hair):         6 pixels wide
+Row 2 (face top):     6 pixels — all skin
+Row 3 (eyes):         6 pixels — skin, eye, skin, skin, eye, skin
+Row 4 (mouth):        6 pixels — skin, skin, mouth, mouth, skin, skin
+Row 5 (body top):     8 pixels — hand, 6 shirt, hand
+Row 6 (body):         6 pixels — all shirt
+Row 7 (legs):         2+2 pixels — with gap in middle
+```
+
+### Scene Composition
+
+#### Chat Dialogue Layout (like our hero image)
+- Two characters on left/right sides, vertically centered
+- Chat bubbles between them, alternating left/right
+- Bubble tails point toward the speaking character
+- Arrows between bubbles show direction of communication
+- Use `orient="auto"` markers for arrow heads
+- Bottom: tagline or decoration
+
+#### Single Character with Label
+- Character centered
+- Label text below
+- Optional: speech bubble above
+
+#### Group Scene
+- Characters spaced evenly
+- Optional: ground line, background elements
+- Keep viewBox tight — no wasted space
+
+### SVG Structure
+```xml
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 W H" font-family="monospace">
+  <defs>
+    <!-- Arrow markers if needed -->
+  </defs>
+
+  <rect width="W" height="H" fill="#fafbfc" rx="12"/>  <!-- Background -->
+
+  <!-- Characters via <g transform="translate(...)"> -->
+  <!-- Dialogue bubbles: <rect> + <polygon> tail + <text> -->
+  <!-- Arrows: <line> with marker-end -->
+  <!-- Labels: <text> with text-anchor="middle" -->
+</svg>
+```
+
+### Chat Bubble Recipe
+```xml
+<!-- Blue bubble (left character speaks) -->
+<rect x="110" y="29" width="280" height="26" fill="#e8f4fd" stroke="#4a9eda" stroke-width="1.5" rx="8"/>
+<!-- Tail pointing left toward character -->
+<polygon points="108,41 99,47 108,46" fill="#e8f4fd" stroke="#4a9eda" stroke-width="1.5"/>
+<rect x="107" y="40" width="3" height="7" fill="#e8f4fd"/>  <!-- covers stroke at junction -->
+<text x="123" y="46" font-size="13px">📄 Message here</text>
+
+<!-- Orange bubble (right character responds) -->
+<rect x="490" y="71" width="280" height="26" fill="#fdf2e8" stroke="#da8a4a" stroke-width="1.5" rx="8"/>
+<!-- Tail pointing right toward character -->
+<polygon points="772,83 781,89 772,88" fill="#fdf2e8" stroke="#da8a4a" stroke-width="1.5"/>
+<rect x="770" y="82" width="3" height="7" fill="#fdf2e8"/>
+<text x="503" y="88" font-size="13px">🤔 Response here</text>
+```
+
+### Arrow Recipe
+```xml
+<defs>
+  <marker id="ar" markerWidth="8" markerHeight="6" refX="8" refY="3" orient="auto">
+    <polygon points="0 0, 8 3, 0 6" fill="#4a9eda"/>
+  </marker>
+</defs>
+<!-- Right arrow (→): x1 < x2 -->
+<line x1="392" y1="42" x2="465" y2="42" stroke="#4a9eda" stroke-width="2" marker-end="url(#ar)"/>
+<!-- Left arrow (←): x1 > x2 -->
+<line x1="488" y1="84" x2="420" y2="84" stroke="#da8a4a" stroke-width="2" marker-end="url(#ar-o)"/>
+```
+
+## Workflow
+
+### Step 1: Understand the Request
+- What characters/objects to draw?
+- What's the scene? (dialogue, portrait, group, diagram)
+- What colors/brand to match?
+- What size? (compact for badge, wide for README hero)
+
+### Step 2: Generate SVG
+- Write to a temp file or project directory
+- Open with a local preview command for visual inspection
+- Keep viewBox tight — measure actual content bounds
+
+### Step 3: Iterate with User
+- User provides feedback on screenshot
+- Common fixes: overlap, arrow direction, spacing, sizing
+- Use `Edit` for small tweaks, `Write` for major redesigns
+- Typical: 2-4 iterations to get it right
+
+### Step 4: Finalize
+- Ensure no personal info in the SVG
+- Clean up: remove unused defs, tighten viewBox
+- Suggest adding to README: `![Alt text](filename.svg)`
+
+## Capability Rule
+
+If the user expects local preview or interactive visual iteration and the current environment cannot open or preview the generated asset, stop and tell the user what needs to be configured. Do not silently downgrade into a write-only path unless the user explicitly asked for that mode.
+
+## Common Pitfalls
+- **Arrow direction**: `orient="auto"` follows line direction. Line going right→left = arrowhead points left
+- **Bubble overlap**: keep 38-44px vertical spacing between rows
+- **Text overflow**: monospace 13px ≈ 7.8px/char, emoji ≈ 14px. Measure before setting bubble width
+- **Character overlap with bubbles**: keep character x-zone and bubble x-zone separated by ≥10px
+- **viewBox too large**: match viewBox to actual content, add ~10px padding
+- **Tail stroke artifact**: always add a small `<rect>` at the bubble-tail junction to cover the stroke line

package/skills/skills-codex/prior-art-search/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: prior-art-search
+description: "Search patent databases and academic literature for prior art relevant to an invention. Use when user says \"现有技术检索\", \"prior art search\", \"专利检索\", \"check patents\", or wants to find relevant prior art."
+argument-hint: "[invention-description-or-path]"
+allowed-tools: Bash(*), Read, Glob, Grep, WebSearch, WebFetch, Write
+---
+
+# Prior Art Search
+
+Search patents and literature for prior art relevant to: **$ARGUMENTS**
+
+Adapted from `/research-lit` for patent-specific searching.
+
+## Constants
+
+- `MAX_PATENT_RESULTS = 20` — Maximum patent documents to analyze in detail
+- `MAX_PAPER_RESULTS = 15` — Maximum academic papers to analyze in detail
+- `SEARCH_YEARS = 10` — How many years back to search
+- `PATENT_DATABASES = "google-patents, espacenet"` — Patent databases to search
+
+## Inputs
+
+Read the invention description from:
+1. `$ARGUMENTS` if it contains technical details
+2. `patent/INVENTION_BRIEF.md` if it exists
+3. `INVENTION_BRIEF.md` if it exists at project root
+
+## Shared References
+
+Load `../shared-references/prior-art-databases.md` for search strategy templates and IPC/CPC classification guidance.
+
+## Workflow
+
+### Step 1: Extract Search Concepts
+
+From the invention description, identify:
+1. **Core inventive concept**: The primary technical contribution (1-2 sentences)
+2. **Technical problem**: What problem it solves
+3. **Key technical features**: 4-6 specific technical elements that define the invention
+4. **IPC/CPC classes**: Predict relevant classification codes (e.g., G06N, G06F)
+
+### Step 2: Patent Search
+
+For EACH search concept, search via:
+
+**Google Patents** (via WebSearch):
+```
+WebSearch: "site:patents.google.com [keywords]"
+WebSearch: "[keywords] patent"
+```
+- Try primary keywords + technical problem keywords
+- Search in English regardless of target jurisdiction
+- For CN inventions, also search Chinese keywords via WebSearch
+
+**Espacenet** (via WebFetch):
+- WebFetch worldwide.espacenet.com/search results for key queries
+- Search by predicted IPC/CPC classes
+
+**Assignee/Inventor Search**:
+- If known companies/universities work in this area, search their patent portfolios
+- WebSearch: "[assignee name] patent [technical area]"
+
+For each potentially relevant patent found:
+- WebFetch the patent page to extract: title, abstract, representative claims, filing date, assignee, current status
+- Record IPC/CPC classification codes
+
+### Step 3: Academic Literature Search
+
+Search the same concepts in academic databases:
+
+1. **Google Scholar** (via WebSearch): `WebSearch "[keywords] site:scholar.google.com"`
+2. **arXiv** (via `/arxiv` if available, or WebSearch): Search for preprints
+3. **Semantic Scholar** (via `/semantic-scholar` if API key set, or WebSearch)
+
+For each relevant paper found:
+- Extract title, authors, venue, year, key contribution
+
+### Step 4: Classification and Analysis
+
+For each reference found, assess:
+
+1. **Relevance**: How closely does it relate to the invention?
+2. **Overlap Risk**: Does it disclose the same or similar technical solution?
+   - HIGH: Anticipates one or more claim elements
+   - MEDIUM: Discloses a related but different approach
+   - LOW: Same general field, different approach
+3. **Relationship**: Is it anticipating, relevant, or merely background?
+
+Organize results by IPC/CPC classification to see the technical landscape.
+
+### Step 5: Freedom-to-Operate Assessment (Preliminary)
+
+Based on the search results:
+- Identify patents with claims that potentially cover the invention
+- Note any expired patents (public domain)
+- Flag areas where claim scope overlap is significant
+
+**Disclaimer**: This is a preliminary assessment only. A professional freedom-to-operate analysis by a patent attorney is recommended before filing.
+
+### Step 6: Output
+
+Write `patent/PRIOR_ART_REPORT.md` with:
+
+```markdown
+## Prior Art Search Report
+
+### Invention Summary
+[1-2 sentence description of the searched invention]
+
+### Search Strategy
+- Keywords used: [...]
+- IPC/CPC classes searched: [...]
+- Databases searched: Google Patents, Espacenet, Google Scholar, arXiv
+- Date range: [year] to present
+
+### Patent References Found
+
+| # | Patent No. | Title | Date | Assignee | IPC/CPC | Key Teaching | Overlap Risk |
+|---|-----------|-------|------|----------|---------|-------------|-------------|
+| 1 | CN... / US... | [title] | [date] | [assignee] | [codes] | [2-3 sentences] | HIGH/MEDIUM/LOW |
+
+### Non-Patent Literature Found
+
+| # | Reference | Title | Authors/Venue | Year | Key Contribution | Relevance |
+|---|-----------|-------|--------------|------|-----------------|-----------|
+| 1 | [DOI/link] | [title] | [authors] | [year] | [1-2 sentences] | HIGH/MEDIUM/LOW |
+
+### Prior Art Landscape
+[Organized by technical approach or IPC class, not just chronological]
+
+### Freedom-to-Operate Preliminary Assessment
+[Which existing patents might block the invention? What is the risk level?]
+
+### Recommendations
+- Suggested claim scope adjustments based on prior art
+- Areas where novelty appears strongest
+- References to watch during prosecution
+```
+
+## Key Rules
+
+- Never fabricate patent numbers or citations. Mark uncertain references with `[VERIFY]`.
+- Search in English AND the target jurisdiction language (Chinese for CN).
+- Patent prior art includes everything published before the priority date, not just patents.
+- Academic papers are valid prior art for both novelty and inventive step.
+- Include expired patents -- they are public domain but still relevant for novelty.