Popular for its size, but the engineering basics lag behind the interest.

♊ 50+ selected Gemini prompts with images, multilingual support, and instant gallery preview. Open-source prompt engineering library

Documentation

81

Install and run instructions9pt55

No install instructions found in the README (−45 pts).

Add a section showing how to install dependencies.

Contributing guide5pt59

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

32

Tests18pt0

No tests detected anywhere in the repository.

Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

No linter or formatter found.

Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

CI/CD14pt40

CI is configured (.github/workflows/sync-approved-to-cms.yml).

Reproducibility6pt70

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 58
    Forks
  • 0
    Releases

Community

  • 62% - Fair
    Community health
  • authors own >50% of commits
  • 500
    Watchers

Responsiveness

  • Median issue response
  • Median PR merge time
  • 2
    Open issues
Repository files26 root entries
  • .github
    Good: CI is configured (.github/workflows/sync-approved-to-cms.yml).
    Good: Issue or PR templates present.
  • docs
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • public
  • scripts
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under Other.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • README_de-DE.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • README_es-419.md
  • README_es-ES.md
  • README_fr-FR.md
  • README_hi-IN.md
  • README_it-IT.md
  • README_ja-JP.md
  • README_ko-KR.md
  • README_pt-BR.md
  • README_pt-PT.md
  • README_th-TH.md
  • README_tr-TR.md
  • README_vi-VN.md
  • README_zh-TW.md
  • README_zh.md
  • README.md
  • tsconfig.json