new rules

Author: hwisu

.cursor/rules/1.general.mdc

@@ -3,8 +3,34 @@ description:
 globs: 
 alwaysApply: true
 ---
-Use these rules throughout the essay-writing process, from brainstorming to final editing. Focus on:
-- A friendly, consistent tone (e.g., “Howdy?”, “Hope it helps”)
-- Concise, logical organization
-- Avoiding unnatural or inappropriate expressions
-- Verifying facts and technical details
+Use these rules throughout the blog-writing process, from brainstorming to final editing. Presented **from the most abstract/metalevel** to the **most concrete**:
+
+1. **Maintain a friendly, consistent tone**  
+   - e.g., “Howdy?”, “Hope it helps”
+
+2. **Keep the organization concise and logical**  
+   - Structure your writing clearly, using headings, short paragraphs, and lists.
+
+3. **Avoid unnatural or inappropriate expressions**  
+   - Ensure the language flows naturally and remains respectful.
+
+4. **Verify facts and technical details**  
+   - Double-check accuracy and relevance of any data, code, or terminology.
+
+5. **Target audience: Backend developers (beginner and above)**  
+   - Tailor explanations and examples to this specific readership.
+
+6. **Use abbreviations whenever possible**  
+   - If the same abbreviation refers to multiple terms, or if a word is generally spelled out, write it out in full.
+
+7. **Use comments only for confusing or ambiguous code**  
+   - Avoid overly detailed JSDoc-style comments; focus on clarity where it’s genuinely needed.
+
+8. **If there are references, present them as a list at the bottom**  
+   - Provide links, documents, or sources for further reading.
+
+9. **Use *italics* for emphasis**  
+   - Highlight key terms or important notes in italics rather than other methods.
+
+10. **Specify the packages and language versions in any code examples**  
+    - e.g., “Node.js 16.0” or “Express 4.0” for clarity and reproducibility.

.cursor/rules/2.brainstroming.mdc

@@ -1,36 +1,21 @@
 ---
-description: 
+description: When you’re in the brainstorming phase
 globs: 
 alwaysApply: false
 ---
-### Idea Development: Brainstorming & Outlining
+When you’re **in the brainstorming phase**, concentrate on the following parts of the list:
 
-#### Initial Ideation (Brainstorming)
-1. **Generate diverse ideas**  
-   Provide a range of potential approaches, perspectives, and concepts related to the topic
-   Include both conventional and creative angles to give options
+1. **Generate Diverse Ideas**  
+   - Brainstorm multiple approaches or perspectives for the topic.  
+   - Encourage both conventional and creative angles.
 
-2. **Ask thought-provoking questions**  
-   Pose questions that help explore the topic more deeply
-   Example: "What are the unexpected connections between these concepts?"
+2. **Ask Thought-Provoking Questions**  
+   - Formulate questions that spark deeper exploration of the topic.  
+   - *Example*: “Are there unexpected connections or parallels worth highlighting?”
 
-3. **Suggest potential resources**  
-   Recommend types of sources that might be valuable for research
-   Example: "Consider exploring recent academic studies on this subject"
+3. **Suggest Potential Resources**  
+   - Recommend research avenues or reputable sources.  
+   - *Example*: “Look into recent industry reports or academic papers on this issue.”
 
-#### Structural Development (Outlining)
-4. **Establish structural clarity**  
-   Follow requested structures precisely (e.g., "Intro, 3–4 main points, and conclusion")
-   Provide clear section headings that capture main concepts
-
-5. **Ensure logical flow**  
-   Organize content in a logical sequence that builds naturally from one point to the next
-   Create connections between sections to maintain cohesion
-
-6. **Maintain brevity and appropriate tone**  
-   Keep outlines concise while preserving key points
-   Adjust formality to match the context, using casual language when appropriate
-
-7. **Bridge from ideas to structure**  
-   Help transition promising brainstormed concepts into organized outline sections
-   Suggest which ideas might work best as main points versus supporting details
+7. **Bridge from Ideas to Structure**  
+   - Begin mapping out which brainstorming concepts might become primary sections versus supporting details.

.cursor/rules/3.drafting.mdc

@@ -0,0 +1,42 @@
+---
+description: Use these guidelines specifically for editing
+globs: 
+alwaysApply: false
+---
+Use these guidelines **specifically for editing**—from initial content review to the final polish—ensuring the writing remains clear, consistent, and aligned with the author’s intent:
+
+1. **Overall Tone & Authenticity**  
+   - Verify that the voice is friendly, consistent, and genuine (e.g., “Howdy?”, “Hope it helps”).  
+   - Eliminate unnatural or inappropriate expressions.  
+   - Preserve the author’s unique style and voice when making edits.
+
+2. **Natural Flow & Readability**  
+   - Identify robotic, stiff, or awkward phrasing.  
+   - Propose improvements for sentence variety, paragraph structure, and transitions.  
+   - *Example*: “This sentence might flow better as: ‘We discovered that most users prefer simplicity over complexity.’”
+
+3. **Grammar & Spelling**  
+   - Correct mistakes proactively, marking deletions (strikethrough) and additions (**bold**) clearly.  
+   - *Example*: “In paragraph two, ‘their’ should be ‘there.’”  
+   - Monitor repetitive errors; maintain consistent usage and style throughout.
+
+4. **Technical Accuracy**  
+   - Flag potentially outdated or incorrect facts, statistics, or code snippets.  
+   - Encourage the author to verify any specialized information.  
+   - Keep the intended audience (e.g., **backend developers, beginner and above**) in mind when suggesting edits.
+
+5. **Tone Moderation**  
+   - Rein in overly hyperbolic or excessive enthusiasm.  
+   - Replace superlatives (“absolutely amazing,” “unbelievably powerful”) with more balanced language.  
+   - *Example*: Transform “This amazingly brilliant feature completely transforms development” into “This useful feature significantly improves development.”
+
+6. **Tagging Guidelines**  
+   - If applicable, ensure tags use **lowercase, hyphenated** formats (e.g., `functional-programming`).  
+   - Keep tags concise (1–3 words) and aim for 3–7 per post.  
+   - Reuse existing tags when possible, mixing broad tags (`programming`) with more specific ones (`algebraic-effects`).  
+   - Proofread tags for typos or inconsistencies before finalizing.
+
+7. **Final Review**  
+   - Suggest reading the text aloud to catch lingering awkwardness or tonal shifts.  
+   - Summarize the piece’s strengths and highlight any last improvements.  
+   - Double-check that edits, tags, and technical details align with the author’s overall goals and style.

.cursor/rules/3.editing.mdc

@@ -0,0 +1,5 @@
++++
+date = '2025-04-08T12:58:12+09:00'
+draft = true
+title = 'Haskelled 0'
++++