claunia/marechai
1
0
Fork 0
mirror of https://github.com/claunia/marechai.git synced 2026-07-08 17:57:08 +00:00
Code Issues 15 Packages Projects Releases Wiki Activity

feat: add templates for company, machine, and software articles for museum website

Browse Source
This commit is contained in:
Natalia Portillo
2026-06-04 19:35:31 +01:00
parent 03cc1590f6
commit 899abfcab3
3 changed files with 96 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
prompts/companies.md Normal file
View File

@@ -0,0 +1,34 @@
Write a factual article for a computer‑museum website about the company or enterprise specified at the end of this prompt.
Use only verifiable information from Wikipedia, period magazines, manuals, corporate filings, and reputable computer‑museum or archival websites.
Do not invent or infer any detail that is not explicitly documented.
The article should include the following topics when information is available:
- Founding history: origins, founders, motivations, and early context
- Corporate mission, initial goals, and the market needs it aimed to address
- Key design or strategic decisions that shaped its products or services
- Major technological, architectural, or business innovations introduced by the company
- Important product lines, platforms, or services (only those directly relevant to the company’s identity)
- Announcement and launch details for major milestones (how, when, where)
- Impact at the time of announcement, launch, and throughout the company’s operational life
- Influence on computing history, the market, users, competitors, and industry standards
- Standards the company followed, contributed to, or created
- Corporate structure, acquisitions, mergers, or reorganizations (only if documented)
- Geographic markets served and regional differences (only if relevant)
- Financial context when available: launch pricing of key products, major funding rounds, or notable economic events
- Workforce, culture, and developer or partner ecosystem (only if documented)
- Decline, transformation, or dissolution (if applicable)
- Legacy and long‑term historical significance
Requirements:
- Use prose for all sections; no schematics.
- If information is unavailable, omit it entirely—do not speculate or create content.
- Use clear, separated sections, but you may choose the section titles.
- Use common, professional language suitable for a museum audience; avoid unnecessary technical jargon.
- Output clean, raw Markdown suitable for direct publication.
- No emojis. No images.
- You may cite non‑Wikipedia sources using Markdown reference-style citations.
- Tables are allowed when appropriate (e.g., timelines, product families, corporate structure).
- Focus strictly on the specific company requested. Do not discuss unrelated subsidiaries, successors, or predecessor companies unless directly relevant.
- If a regional branch or subsidiary is requested, restrict the article to that region’s specifics and ignore global variants.
Now write the article about: XXXXXXXXXXXX

34
prompts/machine.md Normal file
View File

@@ -0,0 +1,34 @@
Write a factual article for a computer‑museum website about the machine specified at the end of this prompt.
Use only verifiable information from Wikipedia, magazines, manuals, and reputable computer‑museum or archival websites.
Do not invent or infer any detail that is not explicitly documented.
The article should include the following topics when information is available:
- History
- Design: what the machine is, how it works, and why its manufacturer chose that design
- Component decisions made by the manufacturer
- Reasons the manufacturer created it
- Announcement: how, when, and where it was announced
- Launch: how, when, and where it was launched
- Impact at announcement, at launch, throughout its commercial life, and in later historical perspective
- Technical specifications (use schematics/tables only in this section)
- Variants (only if it is a family/series; ignore unrelated product lines)
- Standards it followed and standards it introduced
- Launch price in different markets
- Weight and dimensions (only if documented)
- Software ecosystem: third‑party developer reception, involvement, participation, or decline
- Legacy
Requirements:
- Use prose for all sections except Technical Specifications, where tables/schematics are allowed.
- If information is unavailable, omit it entirely—do not speculate or create content.
- Use clear, separated sections, but you may choose the section titles.
- Use common, professional language suitable for a museum audience; avoid unnecessary technical jargon.
- Output clean, raw Markdown suitable for direct publication.
- No emojis. No images.
- You may cite non‑Wikipedia sources using Markdown reference-style citations.
- Tables are allowed.
- Focus strictly on the specific machine requested. Do not discuss successors, predecessors, or unrelated variants.
- If a regional version is requested, restrict the article to that region’s specifics and ignore all others.
Now write the article about: XXXXXXXXXXXX

28
prompts/software.md Normal file
View File

@@ -0,0 +1,28 @@
Write a factual article for a computer‑museum website about the software specified at the end of this prompt.
Use only verifiable information from Wikipedia, magazines, manuals, and other reliable public sources.
Do not invent or infer anything not explicitly documented.
Optional topics (include only when information is available):
- History and development timeline
- What the software is and what it does
- Origins and motivations behind its creation
- Reasons its developers created it
- Announcement details (how, when, where)
- Launch details (how, when, where)
- Impact at announcement and at launch
- Influence on computing, the market, users, competing products, or later software
- Legacy
Requirements:
- Use continuous prose; no schematics unless absolutely unavoidable.
- If information is unavailable, omit the section entirely—do not speculate.
- Use clear, separated sections, but you may choose the section titles.
- Use common, professional language suitable for a museum audience; avoid unnecessary technical jargon.
- Output clean, raw Markdown suitable for direct publication.
- No emojis. No images.
- Tables are allowed.
- You may cite non‑Wikipedia sources using Markdown reference-style citations.
- Focus strictly on the specific software version requested. Ignore predecessors, successors, or unrelated variants.
- If a regional version is requested, focus exclusively on that region and omit global variants.
Now write the article about: XXXXXXXXXXXX