Communitygithub.com

brainzcode/premium-landing

Add a studio or agency build credit to a website footer — "Site by <Studio>" linking to the studio's site. Use when finishing or shipping a site, adding a footer, or when asked for an agency credit, build credit, designed-by line, or attribution. Covers wording, placement opposite the client's copyright, markup for each stack, styling from the host site's tokens, and the sitewide-footer-link SEO footprint when the same credit runs across many client sites.

Qu'est-ce que premium-landing ?

premium-landing is a Claude Code agent skill that add a studio or agency build credit to a website footer — "Site by <Studio>" linking to the studio's site. Use when finishing or shipping a site, adding a footer, or when asked for an agency credit, build credit, designed-by line, or attribution. Covers wording, placement opposite the client's copyright, markup for each stack, styling from the host site's tokens, and the sitewide-footer-link SEO footprint when the same credit runs across many client sites.

Compatible avec✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/brainzcode/premium-landing/tree/HEAD/plugins/premium-landing/skills/build-credit

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Build credit

A studio credit in a client's footer. Add it as part of finishing the footer, not after the client has signed off.

Configure it once

This skill ships with no studio name. Read it from, in order:

  1. An explicit instruction in the request
  2. landing.config.json → credit: { studio, url, wording }
  3. CLAUDE.md in the project or user config
  4. Ask — once — then record it in landing.config.json

Never invent a studio name, and never leave a placeholder in shipped markup. If no studio is configured and the user does not want one, skip the credit entirely. A site that ships crediting the wrong party is worse than one crediting nobody.

{
  "credit": {
    "studio":  "Your Studio Name",
    "url":     "https://yourstudio.com",
    "wording": "Site by"
  }
}

Wording

Site by is the default — it covers design and build without overclaiming either. Pick the honest one:

WordingWhen
Site by …default — design + build
Design & build by …when you want the scope explicit
Built by …build only, someone else designed it
Design by …design only, someone else built it

Write the studio name in full, correctly cased. Link the name only, never the prefix.

Placement

Bottom legal bar, opposite the copyright. That is where people look for it.

© 2026 Client Name. All rights reserved.              Site by Your Studio ↗

The client keeps the copyright — the credit sits alongside it, never replaces it. © 2026 Your Studio on a client site is wrong unless the contract actually assigns it.

One credit per site. Not in the nav, not floating, not a fixed badge. On mobile the legal bar stacks — let it; do not shrink the credit to fit.

Markup

<div class="footer-legal">
  <span>&copy; 2026 Client Name. All rights reserved.</span>
  <span class="footer-credit">
    Site by
    <a href="https://yourstudio.com" target="_blank" rel="noopener noreferrer">Your Studio</a>
  </span>
</div>

rel="noopener noreferrer" is required with target="_blank".

React / Next / Astro — plain <a>, not <Link>; Link is for internal routes. In JSX mind the space: Site by{' '}<a …>.

Styling

Quiet but findable: same size as the copyright, one step brighter, so it reads as interactive without competing.

.footer-credit a { color: var(--ink-2); transition: color .2s ease; }
.footer-credit a:hover {
  color: var(--ink);
  text-decoration: underline;
  text-underline-offset: 3px;
}

Use the host site's tokens. Never hardcode a colour that ignores the design system, and never introduce the studio's brand colours into a client's palette. On a light site the same rule inverts: one step darker than surrounding meta text.

Do not bold it, add a logo, animate it, or give it a background chip.

The SEO footprint — read this

A sitewide footer link with identical anchor text across dozens of client sites is a recognisable pattern. Google has devalued, and in aggressive cases penalised, agency footer link networks. The credit is legitimate, so it does not need nofollow — but:

  • Vary the anchor across clients. Rotate Site by / Design & build by / Built by. Identical anchor text on 200 domains is the footprint; a few natural variants is not.
  • Never keyword-stuff it. Site by Your Studio — SEO agency in <city> is exactly the pattern that gets footer credits discounted. The studio name is the anchor. Nothing else.
  • Use rel="nofollow" only if the client asks, or on sites you would not want associated.
  • One link. Not one per section, not one in the nav as well.

Permission

On white-label or subcontract work, confirm the credit is in scope before adding it — some contracts forbid it. If the engagement is white-label, leave it out and say so rather than shipping it and hoping.

Checklist

  • Studio name from config or the user — never invented, never a placeholder
  • Footer legal bar, opposite the client's copyright
  • Client retains the copyright line
  • Full name, correct case; only the name is linked
  • target="_blank" with rel="noopener noreferrer"
  • Styled from the host site's tokens
  • Readable on mobile (stacked, not shrunk)
  • Anchor varied from the last few client sites; no keyword stuffing
  • Exactly one credit on the site
  • Permitted under the engagement

Individual skills in this repo

This repo contains 7 individual skills — each has its own dedicated page.

brainzcode/premium-landing

Build a complete premium landing page, either replicated from a reference screenshot/URL or designed from a written brief, in HTML, React, Next.js or Astro. Use when asked to build, design, replicate or clone a landing page, marketing page, or one-page site; when handed a design screenshot or Figma/Pinterest reference to turn into code; or when a landing page needs a full premium pass. Covers design tokens, section patterns, the layout traps that silently break grids and marquees, and screenshot-based responsive verification from 320px to 1920px.

brainzcode/premium-landing

Add Lenis smooth scrolling to a site correctly — setup, anchor offsets for sticky headers, scroll locking for modals and menus, reduced-motion handling. Use when asked for smooth scroll, Lenis, momentum/eased scrolling, or when smooth scroll broke a sticky header, a modal lock, or anchor links. Includes the sticky-position trap that only appears at non-zero scroll.

brainzcode/premium-landing

Build true Apple-style liquid glass in the browser — real refraction via SVG displacement maps, chromatic dispersion, specular edges. Use when asked for liquid glass, glassmorphism, frosted/glass cards, glass navbars, or when a blur-based "glass" effect looks flat. Includes the performance trap that makes backdrop-filter stutter on scroll and the contrast trap that makes text unreadable on glass.

brainzcode/premium-landing

Build a premium mobile nav — a hamburger button that morphs into a close X, a full-screen overlay panel with staggered link reveal, scroll lock, focus trap, and reduced-motion handling. Use when asked for a mobile menu, hamburger/burger button, nav drawer, off-canvas menu, or when a menu loses scroll position, still scrolls behind on iOS, leaks Tab focus to the page underneath, or the close button stops responding. Includes the z-index trap that swallows the close button and the iOS rubber-band trap.

brainzcode/premium-landing

Rebuild a design accurately from a supplied reference — a screenshot, PDF page, mockup or live URL — by measuring it numerically instead of eyeballing it. Use when asked to replicate, clone, match or rebuild a design "exactly", "1 to 1" or "with no mistakes", or when a build drifts from its reference. Covers extracting the true content box from a padded screenshot, deriving element positions as percentages, solving object-fit framing, and knowing when a reference cannot be matched.

brainzcode/premium-landing

Ship link previews and favicons that actually work - Open Graph and Twitter card tags, a correctly framed 1200x630 share image, and a full favicon set (SVG, ICO, apple-touch, maskable manifest icons). Use when asked for social sharing, OG image, open graph, twitter card, link preview, share image, favicon, app icon, apple touch icon, or web manifest. Also use when a shared link previews blank, shows the wrong image, or a favicon will not appear. Includes the absolute-URL trap that silently blanks every preview and the font trap that breaks SVG favicons on other machines.

brainzcode/premium-landing

Source free, licence-clear photography for a site from Unsplash — searching by mood rather than noun, sizing and cropping for the slot, honouring the API's hotlink and download-tracking requirements, and writing real alt text. Use when a page needs a hero image, section photography, avatars or card art and none was supplied; when placeholder greys need replacing with real imagery; or when asked to find, pick or swap photos for a design.

Skills associés