writing-types
Write Modular Next.js Types
Next.js projects can collect large type files that are hard to maintain. This skill guides Claude, Codex, and Claude Code to write small TypeScript types and interfaces in srs/types.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "writing-types" from https://skillstore.io/skills/emz1998-writing-types.md and its manifest at https://skillstore.io/api/skills/emz1998-writing-types/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "writing-types". Create types for a user profile settings page.
Expected outcome:
The response proposes separate profile, preferences, and notification type files, each kept short and focused.
Using "writing-types". Split a long list of checkout interfaces.
Expected outcome:
The response groups checkout, payment, and address definitions into separate files with clear naming.
Using "writing-types". Review my proposed type layout.
Expected outcome:
The response flags crowded files, suggests smaller modules, and checks whether files stay near the 50 line limit.
Security Audit
SafeBoth static external command findings are false positives caused by Markdown inline code around the srs/types path. SKILL.md contains only prose instructions for organizing TypeScript types and interfaces, with no executable code or command instructions. No evidence found of prompt injection, data exfiltration, or other semantic abuse.
Risk Factors
⚙️ External commands (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/emz1998-writing-types/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/emz1998-writing-types?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/emz1998-writing-types?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emz1998-writing-types/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/emz1998-writing-types.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Emz1998. (2026). writing-types security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/emz1998-writing-types/audits/4BibTeX citation
@techreport{emz1998-emz1998-writing-types-2026,
author = {Emz1998},
title = {writing-types security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/emz1998-writing-types/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "writing-types security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "Emz1998"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/emz1998-writing-types/audits/4"
identifiers:
- type: other
value: "skillstore:emz1998-writing-types:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Create feature types
Define compact types and interfaces for a new Next.js feature without growing a shared type file.
Split crowded definitions
Refactor a large type collection into smaller files that are easier to scan and maintain.
Review type organization
Check whether proposed type files follow the modular structure and file length guidance.
Try These Prompts
Use the writing-types skill to create TypeScript types and interfaces for a profile settings feature in a Next.js app.
Use the writing-types skill to organize order, customer, and payment type definitions into modular files under srs/types.
Use the writing-types skill to split an oversized type file into smaller files while preserving clear names and imports.
Use the writing-types skill to review these proposed Next.js type definitions for modularity, file size, and interface placement.
Best Practices
- Give the feature name, expected data shapes, and current folder layout.
- Ask for small files with clear names before requesting implementation code.
- Review generated imports and names against your project conventions.
Avoid
- Do not place unrelated domain models in one shared type file.
- Do not ask the skill to run TypeScript checks or project tests.
- Do not treat the 50 line rule as more important than readable definitions.