AddThisFeature

Certificate Generator

Issue a personalised certificate people can download, print, or share on completion.

moderate Documents & Files

What it adds

A certificate record and rendered document tied to a completed achievement, with a public verification page.

What your agent is told to do

5
  1. 1

    Trigger issuance from the achievement the app already tracks, so a certificate exists because something was completed rather than because someone visited a page.

  2. 2

    Store the recipient name, achievement title, issue date, and issuer details on the certificate record itself. Reading them from live accounts means a name change would rewrite certificates already in circulation.

  3. 3

    Render through the app's existing PDF Export path and reuse the app's brand assets rather than introducing a second set of fonts and logos.

  4. 4

    Give every certificate a stable public verification URL that shows what was issued, to whom, when, and whether it is still valid.

  5. 5

    Do not put personal data beyond the recipient's name and the achievement on the public verification page. It is a link people paste into profiles and it will be crawled.

Edge cases it handles

8
  • Long names, long course titles, and names in scripts with tall glyphs will overrun a fixed-width line and collide with the border. Shrink or wrap within a defined box and test with a name of sixty characters before shipping.
  • A certificate with no way to check it is worth nothing to the person reading it. Give each one a verification page reachable from an identifier printed on the document, and keep that page working even after the recipient's account is closed.
  • When the underlying achievement is revoked, corrected, or retaken, the old certificate must be marked revoked or superseded on the verification page rather than silently deleted, because copies are already downloaded and circulating.
  • A document rendered at screen resolution prints blurry and looks cheap. Render at print resolution with vector text and embedded fonts, and size the page to a standard sheet.
  • Editing the template must not alter certificates already issued. Version the design and keep each certificate bound to the version it was issued under, so a redesign does not rewrite history.
  • The verification identifier must not be sequential or guessable, or anyone can enumerate every certificate the app has ever issued.
  • Recipients will share the certificate on social platforms, so the verification page needs a title and preview image that render sensibly when unfurled.
  • A recipient who downloads twice should get the same document, not a freshly dated one.

Definition of done

9
  • Completing the tracked achievement issues a certificate with the recipient and date recorded on it.
  • Names and titles up to a defined length render inside the layout without overlap or clipping.
  • Every certificate carries an identifier that resolves to a public verification page.
  • Revoking or superseding an achievement is reflected on the verification page.
  • Documents render at print resolution on a standard page size with embedded fonts.
  • Template changes are versioned and do not alter previously issued certificates.
  • Verification identifiers cannot be enumerated.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.