localdocs-til-link
Links a project's localdocs/ folder to the TIL repository via symlink for centralized document management. Use when setting up a new project, after accidentally deleting localdocs/, or when connecting localdocs/ to a TIL repo for git-backed persistence. Triggered by requests like "link localdocs to TIL", "setup localdocs symlink", or "/localdocs-til-link 802 that-night-sky".
Best use case
localdocs-til-link is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Links a project's localdocs/ folder to the TIL repository via symlink for centralized document management. Use when setting up a new project, after accidentally deleting localdocs/, or when connecting localdocs/ to a TIL repo for git-backed persistence. Triggered by requests like "link localdocs to TIL", "setup localdocs symlink", or "/localdocs-til-link 802 that-night-sky".
Teams using localdocs-til-link should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/localdocs-til-link/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How localdocs-til-link Compares
| Feature / Agent | localdocs-til-link | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Links a project's localdocs/ folder to the TIL repository via symlink for centralized document management. Use when setting up a new project, after accidentally deleting localdocs/, or when connecting localdocs/ to a TIL repo for git-backed persistence. Triggered by requests like "link localdocs to TIL", "setup localdocs symlink", or "/localdocs-til-link 802 that-night-sky".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# localdocs-til-link
Connects a project's `localdocs/` to the TIL repo via symlink. Real files live in TIL (git-managed); the project sees `localdocs/` as if it were a normal directory.
## Prerequisites
Ask the user for the following if not provided as arguments:
- **TIL folder name** — the subdirectory inside TIL for this project, e.g. `"802 that-night-sky"`
- **TIL_BASE** — absolute path to the TIL repository root, e.g. `~/20_DocHub/TIL`
Resolve `TIL_BASE` to an absolute path before use (expand `~` if needed).
- `PROJECT_LOCALDOCS={project_root}/localdocs`
## Workflow
### 1. Check current state
```bash
ls -la {PROJECT_LOCALDOCS}
ls "{TIL_BASE}/{til_folder}"
```
- If `localdocs/` is already a symlink (`->` in `ls -la`), stop and inform the user.
- If the TIL folder doesn't exist, confirm with the user before creating it.
### 2. Merge (when both sides have files)
Copy TIL → localdocs, no overwrite:
```bash
rsync -av --ignore-existing "{TIL_BASE}/{til_folder}/" "{PROJECT_LOCALDOCS}/"
```
For files with differing timestamps, show the diff and ask the user which side is authoritative.
### 3. Move and create symlink
```bash
rm -rf "{TIL_BASE}/{til_folder}"
mv "{PROJECT_LOCALDOCS}" "{TIL_BASE}/{til_folder}"
ln -s "{TIL_BASE}/{til_folder}" "{PROJECT_LOCALDOCS}"
```
### 4. Verify
```bash
ls -la {PROJECT_LOCALDOCS} # confirm symlink (look for ->)
ls "{TIL_BASE}/{til_folder}/" # confirm files are present
```
## Notes
- `localdocs/` must be in the project's `.gitignore`. If missing, recommend adding it.
- Always quote paths containing spaces.
- After setup, remind the user to commit in the TIL repo.Related Skills
worklog
Update worklog files by moving tasks between todo/doing/done states. Use when recording task progress, starting new work, or marking tasks complete. Requires explicit arguments: worklog [done|doing|todo] [description].
template-proposal-review
Review proposal files in localdocs/localdocs/proposals/ and decide whether to apply them to the upstream python-project-template repository. Use when evaluating proposals generated by template-upstream, deciding which ones to accept or reject, and applying accepted ones to the template repo. Triggers on: "proposal 검토", "제안 검토", "template에 반영할지", "proposals 리뷰", "upstream 반영 결정".
template-downstream
Update .claude/, .mcp.json, and .pre-commit-config.yaml from the upstream python-project-template repository into the current project. Only files that exist upstream are updated — project-only files are never deleted. Use when pulling latest tooling, rules, hooks, or skills from the canonical template into this project. Triggers on: "템플릿 최신화", "template sync", "upstream 반영", "template 업데이트".
template-broadcast
Apply template-downstream to all registered downstream projects in bulk, one project at a time. Use when you want to push the latest .claude/, .mcp.json, or .pre-commit-config.yaml to every project at once. Triggers on: "일괄 배포", "전체 프로젝트에 내려보내기", "모든 프로젝트 업데이트", "broadcast template", "bulk sync".
tdd
Test-Driven Development workflow. Use for ALL code changes - features, bug fixes, refactoring. TDD is non-negotiable.
sparks-create
Apply the 13 thinking tools from "Sparks of Genius" (생각의 탄생) to reframe any problem through creative, cross-disciplinary lenses. Use when conventional analysis falls short, when you need a fresh creative angle, or when the problem spans multiple domains.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
rethink-unblock
Break out of a stuck approach by reframing a technical problem through structured thinking frameworks. Use when blocked, going in circles, or when a fresh perspective is needed on architecture, design, or debugging.
refactoring
Refactoring assessment and patterns. Use after tests pass (GREEN phase) to assess improvement opportunities.
python-mcp-expert
Expert assistant for developing Model Context Protocol (MCP) servers in Python. Use when creating, debugging, or optimizing MCP servers with FastMCP, tools, resources, and prompts.
python-conventions
Python coding conventions and guidelines including PEP 8, type hints, docstrings, and testing standards. Automatically applied when working with Python files.
prd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.