agentsclimarketplace

Portfolio direction

Skill obadadallo95/ai-native-portfolio-skills/skills/portfolio-direction

An opinionated skill system for AI-native builders who want portfolios with real identity, proof, taste, and AI discoverability.

Install
npx -y skills add obadadallo95/ai-native-portfolio-skills --skill portfolio-direction

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Defines the visual, structural, and narrative direction of a portfolio so it feels authored, premium, and strategically positioned instead of generic or template-like.

SKILL.md

2.6 KB, 512 tokens by cl100k_base, as published. Nobody here has run it

Portfolio Direction

This skill defines how a portfolio should feel, not just how it should look.

It exists to protect a portfolio from:

  • generic SaaS aesthetics
  • AI-slop layouts
  • shallow project presentation
  • overdecorated motion
  • identity drift

Core Intent

The portfolio should present the builder as:

  • someone with taste
  • someone with product judgment
  • someone with a point of view
  • someone whose work is structured, not accidental

The portfolio is not:

  • a gallery of nice screens
  • a resume with gradients
  • a list of tools
  • a generic landing page with personal branding on top

It is a controlled narrative about:

  • who the builder is
  • how the builder thinks
  • what kind of work they carry
  • why their work deserves attention

Visual Direction

The visual language should feel:

  • intentional
  • controlled
  • premium
  • specific
  • expressive without becoming childish
  • modern without becoming trend-chasing

Favor

  • strong hierarchy
  • asymmetry when it helps emphasis
  • type systems with contrast
  • restrained motion
  • proof-led sections
  • clear section roles
  • surfaces that feel selected, not busy

Avoid

  • equal-weight cards everywhere
  • default AI startup aesthetics
  • decorative motion with no narrative role
  • loud gradients compensating for weak structure
  • sections that all look like the same component with new copy

Section Rule

Every major section should answer a real question.

Examples:

  • Hero: who is this person and why should I care?
  • Work: what did they build and what does it prove?
  • Case studies: how did decisions change the product?
  • About / manifesto: what kind of builder are they really?
  • Contact: what should I do next if I trust them?

If a section cannot answer a real question, simplify or remove it.

Project Rule

Projects should communicate:

  • hierarchy
  • context
  • decisions
  • transformation
  • evidence

A project section should privilege:

  • story over screenshot
  • structure over surface novelty
  • decision-making over decoration

Taste Rule

If a design choice makes the portfolio:

  • more generic
  • more crowded
  • more performative
  • less clear
  • less authored

it should probably be rejected.

Success Condition

This skill succeeds when the portfolio feels like:

  • a builder's world
  • a coherent point of view
  • a selected body of work
  • a site that could only belong to this person

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.