flashcards-open-source-app: Skill for Codex

Publish a public flashcard deck

Reference

Before drafting, inspect one published deck. GET https://api.flashcards-open-source-app.com/v1/catalog now redirects to an immutable CDN artifact holding the complete public JSON snapshot, so a plain curl needs -L to follow it; do not use that endpoint for reference and do not use it for per-deck verification. The only sanctioned read of that snapshot is the one step 8 names. Read one deck and at most five of its cards through bounded endpoints:

package_json="$(curl --fail --silent --show-error 'https://api.flashcards-open-source-app.com/v1/catalog/packages?limit=1')"
printf '%s\n' "$package_json" | jq '.catalogPackages[0]'
package_version_id="$(printf '%s\n' "$package_json" | jq -r '.catalogPackages[0].latestVersion.packageVersionId')"
curl --fail --silent --show-error "https://api.flashcards-open-source-app.com/v1/catalog/package-versions/${package_version_id}/cards?limit=5" | jq '.cards'

Product defaults

• For a standardized full-course deck, do not block on the learner's current topic or school textbook. Confirm the curriculum edition, level, language, and exam session only when they change scope, then build a complete internal coverage ledger.
• Optimize title, slug, and description strongly for the exact learner query while remaining accurate, useful, and rights-safe. Put the primary course or exam query first when it accurately identifies the content. Verify applicable naming and trademark rules before using a third party's course, exam, or standard name; never use its logo or trade dress or imply official status, affiliation, or endorsement. Keep the public title and canonical slug evergreen for a stable curriculum; use the current year only in separate SEO metadata or a visible Reviewed for <year> line after an annual compatibility check. Preserve one package and URL across compatible years.
• For an independently authored common-knowledge deck intended for unrestricted reuse, default the license field to Common knowledge · CC0 1.0 and keep it label-only. Apply CC0 to original questions, answers, organization, metadata, and original or LLM-generated media to the extent applicable rights exist. Put scope, provenance, and non-affiliation language in the description. Do not claim ownership of facts or license rights the publisher does not hold.
• When a course or examination owner is named, end the description with an independent, unofficial, non-affiliation notice; state that no examination questions, mark schemes, or curriculum text were copied when true; and link the owner's official requirements page. Keep these statements outside the license field.
• Default to no third-party media. Create original or LLM-generated visuals from facts with an independent composition; do not trace or redraw a specific source image. Use third-party media only when the user explicitly requests it and its provenance, license, attribution, and intended reuse are verified.
• Public catalog cards support optional images and LaTeX math; use either only when it materially improves the content. Write $...$ inline for a short expression inside a sentence, with no space just inside either $ and no digit right after the closing $; write a standalone display formula as its own block, with $$ alone on the opening and closing lines and a blank line before and after it or the start or end of the card side, because a $$ block that does not stand alone stays literal. Escape a currency $ as \$ (\\$ inside JSON such as cards.json). Put math only in a plain paragraph that holds no link, image, bold, italic, strikethrough, or code anywhere in it, and keep it out of headings, lists, tables, blockquotes, code blocks, and raw HTML, and off any card side using reference-style link or image definitions; anywhere else it stays literal.
• Default to one short, recognizable root tag on every card. For a large deck, allow one coarse group tag in addition to the root; never exceed two tags per card or create a deeper public hierarchy by default. Use clear abbreviations, merge small topics into broader groups, and keep fine topics, difficulty, source-specific syllabus codes, and production statuses internal. Before drafting a large deck, state every public tag and the target card count for each group.