trkaplan

FlickPick: AI-Powered Movie Assistant - Design Document

Date: November 18, 2025
Status: Approved Design
Category: Mobile Application - Entertainment

---

Executive Summary

trkaplan

#!/bin/bash

CLAUDE_DIR="$HOME/.claude"
SETTINGS="$CLAUDE_DIR/settings.json"
ZAI_SETTINGS="$CLAUDE_DIR/settings_zai.json"

# Renkler
GREEN='\033[0;32m'
BOLD='\033[1m'
RESET='\033[0m'

trkaplan

#!/bin/bash

################################################################################
# AUTONOMOUS AI TASK PROCESSOR
# https://gist.github.com/nibzard/a97ef0a1919328bcbc6a224a5d2cfc78
################################################################################
#
# PURPOSE:
#   Runs Claude Code in a fully autonomous loop to process tasks from a todo
#   file without human intervention. The AI agent will continuously select,

trkaplan

Create .http files to Interact with our API endpoints.

Your task: Is to take our API endpoints that are listed and create the API.md file for us to use in our editor to make requests via the vscode-restclient extension.

Follow this process:

1. Identify Recent Project Developments:
   • Review information about recently completed tasks (e.g., from docs/tasks/, task management systems if accessible, or summarized in recent discussions).
   • Examine recent commit history for significant changes to code, features, or configurations.

• Consider any new features added or bugs fixed that might impact documentation.

trkaplan

You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.

Project Context: This is a dev tool built for evaluating open source projects allowing people to better understand the maintainability, activity and longevity of a given project to allow devs to better decide whether they should include or use the given open source repositories after the analysis 

Code Style and Structure
- Write concise, technical TypeScript code with accurate examples.
- Use functional and declarative programming patterns; avoid classes.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
- Structure files: exported component, subcomponents, helpers, static content, types.

trkaplan

Playwright E2E Testing Guidelines

Test Structure and Organization

• Store all tests under the tests/ folder
• Name test files based on the system component being tested (conceptual, not React component)
• Group related tests within a single file using test.describe blocks
• Use descriptive test names that explain the functionality being tested
• use test.use({storageState: ...}) for setting auth state across all test in the suite

Locator Strategy

trkaplan

[Project Name]

Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.

Project Context

[Brief description ]

• [more description]
• [more description]
• [more description]

trkaplan

const fs = require('fs');
const cp = require('child_process');
const util = require('util');
const path = require('path');

const exec = util.promisify(cp.exec);
const writeFile = util.promisify(fs.writeFile);

const prettierConfigVscode = {
    'editor.codeActionsOnSave': {

trkaplan

Çoğu proje Eslint konfigürasyonu ile geldiğinden ve editörümüzde eslint eklentisi kurulu olduğundan biliyor sanıyor olduğunuz bir şeyi netleştirelim: Sorun; build anında aldığımız eslint hatalarını kodu yazıp kaydettiğimiz anda otomatik düzeltilmesini sağlamak: (Eğer linterin bunu düzeltme imkanı varsa, çünkü bazı eslint uyarıları otomatik fixlenemiyor) Lint hatasını almışsak, projede bir linting konfigürasyonu var demektir. Editörde bu hataları görebilmek için eslint eklentisine ihtiyaç duyuyoruz. https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint

Editörde değişiklikler kaydedildiğinde linterın otomatik çalışması için de vs code için; settings.json içinde şu ayara ihtiyaç var:

trkaplan

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example