portfolio-conventions

Solid

Portfolio coherence rules — preloaded into troubleshooter and portfolio-sync agents as background knowledge.

AI & Automation 2 stars 0 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
16
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Portfolio Conventions These are the active portfolio-wide rules. This skill is preloaded — do not invoke it manually. ## Identity - Each app has its own visual identity, name, and universe. No shared design system. - Coherence comes from: author signature, quality standards, portfolio site, and automated sync. - Portfolio site: {portfolio-site-url} — data-driven from portfolio-apps.json. - GitHub username: {github-username}. Dev directory: ~/Dev. ## Naming - All repos use kebab-case matching the folder name in ~/Dev. - No unintentional naming patterns (the "-or" suffix issue prompted Unbiasor → Untilt). - New projects default to sort_order: 99. ## Signature - Footer: "Made with care by {author-first-name}" with link to https://{portfolio-site-url}. - Present by default on all apps. Opt-out must be explicit in project CLAUDE.md. ## Dark/Light Mode - All user-facing apps support dark and light mode via prefers-color-scheme. - Manual toggle is optional per project. Opt-out requires justification in CLAUDE.md. ## Documentation - README: description, stack, local dev, deployment. Created at project init, never boilerplate. - CLAUDE.md: project-specific only, never duplicates global rules. Written in English. - .portfolio.yml: machine-readable manifest at repo root. Updated in same commit as any field change. ## Manifest (.portfolio.yml) Required fields: name, slug, tagline, description, audience, visibility, status, surface_type, url, portfolio_card, portfolio_link,...

Details

Author
w2ur
Repository
w2ur/claude-code-setup
Created
4 months ago
Last Updated
2 days ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

portfolio

Plan, build, critique, update, or ship a professional design portfolio as one evidence-backed system. Use when the user invokes /portfolio; needs portfolio positioning, project inventory and selection, personal brand, case studies, homepage/about/contact copy, information architecture, visual direction, website implementation, accessibility, review, or publishing; or wants to turn scattered work into a coherent portfolio for a specific role, client, or audience.

0 Updated 5 days ago
jpoindexter
AI & Automation Listed

portfolio-audit

Audits, renders, and bootstraps the cross-repository capability portfolio across `nolte/*` per `spec/portfolio/portfolio-management/`. Audit dispatches portfolio-manifest-collector agent for read-only inventory collection, then detects capability duplicates, surfaces gaps, verifies tech-stack consistency per `spec/portfolio/tech-stack/`, and writes a Findings-Report under `.audits/portfolio/` using Critical / Warning / Suggestion / Info severities. Render regenerates the aggregated inventory under the per-language docs/ portfolio subtree. Bootstrap creates a repository's first `project/portfolio.yml`. Invoke when the user asks to "audit the portfolio", "check for portfolio duplicates", "render the portfolio inventory", "discover the tech stack" (audit view), or equivalent German-language requests. Don't use to consolidate duplicates (operator opens cross-repo PRs), to author new capabilities, or for per-repo tech_stack capture or refresh (use tech-stack-capture). Supports resume on re-invocation.

0 Updated today
nolte
Data & Documents Listed

project-portfolio

Use this skill when the user is thinking about their work across many projects at once, over time, rather than the single repo or file in front of them. Trigger it when they ask where things stand across everything they're juggling, what to focus on or do next, or for a weekly/periodic review of what's in flight or gone stale; when they want to start keeping track of ongoing efforts scattered across folders (side projects, a job hunt, open pull requests, writing, personal goals) so they stop losing the thread; when they check whether anything changed since they last synced or need to respond to; when they report progress on a weeks-or-months-long effort; or when they wrap up a session and say to log, save, or remember where they left off. This is a persistent, cross-session tracker for long-lived work — not for planning a single task, one-repo status, or one-off questions about the current codebase.

1 Updated 1 weeks ago
mc856